Invoices

The Invoices page (sidebar → Invoices) is the accounts-receivable view: what buyers and channels still owe you, how overdue it is, and the full detail behind any single invoice.


Overview

Open Revenue → Invoices. The page has four summary cards, an aging chart, and a filterable invoice table; select any row to open its full record. The cards cover every invoice, whatever the date range, while the table starts at invoices issued in the last 90 days. The amounts the page works from are seller amounts due — what is still owed to you on each invoice, after marketplace fees — not what the buyer still owes; Three amounts on every invoice explains the difference. For the money on its way to you — payouts and installments — see Cash & Disbursements.

Invoices page: AR summary cards, aging buckets, and the invoice table

Summary cards

CardMeaning
Total OutstandingSum of the seller amounts still due, in US dollars, excluding paid, draft, voided, and written-off invoices. While any invoice in scope has an unknown balance, it adds up the known ones and says Known balances only beneath.
DSODays Sales Outstanding — total outstanding as a share of everything invoiced, expressed in days, from the invoices whose balance and amount are both known.
At Risk (90+)Seller amount due in the oldest aging bucket, from the invoices whose balance is known.
Open InvoicesCount of invoices with a seller amount still due, plus the invoices whose balance is unknown. Drafts, voided, and written-off invoices are never counted.

Accounts Receivable summary cards with each value circled

Left to right: ① Total Outstanding, ② DSO (in days), ③ At Risk (90+), and ④ Open Invoices (a count, not an amount).

Select a card to filter the invoice table by it: Total Outstanding and Open Invoices list the Open invoices, and At Risk (90+) the open invoices in the Over 90 bucket — of every issue date, because the cards cover every invoice whatever the date range. Select the card again to clear the filter. DSO does not filter the table.

The table shows every amount in its invoice’s own currency. The cards and the aging chart convert each invoice to US dollars first: with the rate stored on its revenue records when they carry one, otherwise with Fours’ daily exchange rate from on or before the invoice date. An invoice that can’t be converted that way is treated like one with an unknown balance, below.

Some balances can’t be known yet. When Fours does not have the evidence to work out what is still owed on an invoice — for example, a GCP payout it cannot attribute to a single invoice — the invoice’s status reads Unknown balance and its seller amount due reads —, rather than a guessed figure. A note under the cards counts these invoices together with the ones that have no US-dollar exchange rate (2 invoices have unknown balances or USD exchange rates. Metrics exclude unavailable USD amounts.). They count toward Open Invoices and are listed by the Open status filter, but they are left out of the aging chart and At Risk (90+). Total Outstanding then adds up only the balances it knows and says Known balances only beneath, or reads — when it knows none. DSO is worked out from the invoices whose balance and amount are both known and says Known balances only, or reads — with Unavailable: incomplete balances when no invoice qualifies. Seller amount due lists what makes each channel’s balance unknown.

Aging buckets

The aging chart splits outstanding seller amounts due, in US dollars, into Current, 1–30, 31–60, 61–90, and Over 90 days. An invoice is included while it has a known seller amount due above zero that can be converted to US dollars, and is not a draft, voided, or written off.

Aging is computed when you read it, not on a schedule. Every page load works out each invoice’s bucket from its due date against today’s date — days overdue are the whole days since that date, and an invoice with no due date counts as current — unless a bucket is already stored on the invoice, which then takes precedence. The same rule applies to every invoice, whoever owes it. There is no aging job to wait for: once an invoice whose bucket comes from its due date crosses into the next bucket, it shows there the next time you open the page.

Each bar shows the bucket’s total balance and invoice count; Export CSV downloads the underlying invoices (one row each, with the table’s columns, its aging bucket, and the Partner Fee Status, Partner Fee Group, and Currency columns), not the bucket-level totals. The export lists every invoice with a known seller amount due above zero, each in its own currency, so it can include invoices the chart leaves out for having no US-dollar exchange rate — as the note on the chart card says.

AR aging buckets with the Current and 90+ balances circled

Here the bulk of the balance sits in ① Current (not due), while ② 90+ days overdue isolates the at-risk balance and its invoice count — the same figure surfaced by the At Risk (90+) card.

Working invoices

The invoice table lists the invoice ID, buyer name, channel, issue and due dates, invoice amount, collectable amount, partner fee as an amount (Partner Fee) and as a percentage (Partner Fee %), Seller Amount Due, status, and aging, and ends with Actions: a Download PDF icon and View Details. A column chooser lets you show and hide columns, and the table can be sorted by issue date, due date, collectable amount, and partner fee. On an AWS invoice built from a revenue record, the two partner-fee columns are calculated the same way as on Revenue Records — the amount includes the VAT AWS charges on its listing fee, and the percentage does not; see Reading the AWS partner fee. When an AWS invoice’s collectable amount or fee is unknown to Fours, both columns read — rather than a calculated fee. On a GCP invoice, Partner Fee shows the fee when one of Google’s reports that state it (Detailed Disbursements, or Charges and Usage) confirms it for that invoice. When Fours can confirm a fee only for the group of charges the invoice belongs to, it shows View order partner fee with Individual fee unavailable beneath — see Order partner fee details — and otherwise it reads Unavailable. Partner Fee % is the confirmed fee over the fee base Google reported, and reads — without one; see Reading the GCP partner fee. The Partner Fee amount is in the invoice’s own currency, shown with that currency’s usual decimal places; Partner Fee % is rounded to two decimal places.

To move a column, drag its header; the first column stays first. The columns you show and their order are remembered in this browser. On an entitlement’s or buyer’s Invoices tab the headers don’t drag.

To see only the invoices for one agreement, open the entitlement instead: an entitlement’s detail page carries Invoices (n) and Disbursements (n) tabs, each already scoped to that entitlement. Filter by search, status (Open, Draft, Invoiced, Overdue, Partially Paid, Paid, Disbursed, Refund pending, Refunded, Written Off, Voided; Invoiced finds the invoices whose status reads Sent), aging bucket, date range, and channel. An invoice from Fours’ own invoice records reads Disbursed once its revenue record carries a disbursement reference number or a payment ID — on AWS, only once its seller amount due is also 0 — unless it is a draft, voided, or written off; an invoice built from a revenue record never takes that status. A Stripe, Azure, or GCP invoice never reads Disbursed: its status follows its balance — Draft, Sent (shown as Invoiced in the filter), Overdue, Partially Paid, Paid, or Unknown balance. A GCP invoice reads Refunded instead of Paid once its seller amount due is 0 and a refund on it has succeeded; a Stripe or Azure invoice never reads Refunded. Unknown balance has no filter option of its own; the Open filter includes it, and leaves out drafts, voided, and written-off invoices. An AWS invoice whose refund credit AWS has issued but not yet settled reads Refund pending, and Refunded once the refund settles. Its detail view then notes that the buyer’s balance already includes the credit, while the seller amount due and aging still count the marketplace funds that have not settled. Search matches the IDs and other values stored on the invoice — invoice, buyer, entitlement, and product IDs, for example — and also the buyer names shown in the table, as a case-insensitive substring.

When nothing matches, the table says why and offers a way back: No invoices match “<search>” with Clear search; Show all time when the issue-date range hides the rest; or Clear filters, which resets the status, aging, and channel filters. An organization with no invoices at all reads No invoices yet. Connect a revenue channel to start ingesting invoices.

Export CSV, at the end of the table’s toolbar, downloads every invoice that matches the table’s search, status, aging, issue-date range, and channel — from all pages, not just the rows on screen — with the columns you show, in the table’s order, each amount in its invoice’s own currency, followed by three more columns: Partner Fee Status (CONFIRMED or UNAVAILABLE; on GCP INVOICE, ORDER, or UNAVAILABLE), Partner Fee Group (the GCP order-level fee groups the invoice belongs to), and Currency. An order-level GCP fee is never written into an invoice’s Partner Fee column; the GCP Order Partner Fees report lists each one once. The file is invoices_<date>.csv; Saved views describes the dialog. An entitlement’s or buyer’s Invoices tab has the same Export CSV, limited to that entitlement or buyer. The aging chart’s Export CSV is a separate download (see Aging buckets).

To inspect a single invoice:

  1. Find the invoice in the table — use search or the status/date/channel filters to narrow the list.
  2. Select View Details on its row.
  3. Review the record — billing and contract terms, financials, and settlement — alongside a lifecycle timeline (issued → payment applied → disbursed/swept → written off). The Contract section names the Offer and the Entitlement — and any Related entitlement the invoice also covers — with each one’s ID beneath its name and its current status beside it; each links to its own page.
  4. Select Back to invoices to return to the list.

In the Billing section, Buyer Payment Terms is the buyer’s net terms in days: the terms stored on an invoice from Fours’ own invoice records, otherwise the term the buyer accepted on AWS, or else the whole days from the invoice date to the due date. The PDF statement shows them as Net N days.

Invoice detail: billing, contract, financials, and provider references with a lifecycle timeline

The header strip summarizes the invoice at a glance — the circled items below are the invoice ① status (Paid, Sent, Overdue, Disbursed, …) and its ② amount, with seller amount due, amount paid, and aging bucket beside them. The image predates the Seller amount due tile, which replaced Balance due there:

Invoice detail header with status and amount circled

Three amounts on every invoice

The Financials section separates what the buyer paid, what the buyer still owes, and what is still owed to you — three amounts that differ whenever a marketplace takes a fee or a refund applies:

AmountWhat it means
Amount paidWhat the buyer has paid against the invoice, gross — before marketplace fees and refunds.
Balance dueWhat the buyer still owes, gross: the invoice amount less refunds that apply and the amount paid.
Seller amount dueWhat is still owed to you on the invoice — by the marketplace or the buyer — after marketplace fees and confirmed payouts. This is the amount the table, the cards, and aging use.

Any of the three reads — when the channel has not supplied the evidence for it. Each channel’s formula is in KPI calculation formulas.

Invoice chain

When AWS has credited an invoice, the invoice’s detail opens with an Invoice chain panel, above the lifecycle timeline. It lists the invoice’s accounting documents — the Original invoice, each Credit memo (a negative amount), and the Replacement invoice when AWS issued one — with each one’s Invoice ID, Date, and Amount, headed by Net invoiced: the sum of those lines.

Fours links a replacement only after a full credit, and only to an AWS invoice that has no credit of its own, for the same amount, product, entitlement, buyer, currency, agreement, offer, and service period, issued within 14 days after the credit. The replacement’s own detail shows the same chain. When no invoice qualifies, the panel says Replacement not linked; when more than one could be the replacement, or one invoice could replace more than one credit, it says Replacement link needs review and links none.

The panel appears only while the credit is in effect — not failed or canceled — and when the credit memos Fours recorded from AWS’s billing-event feed add up to the credited amount, in the invoice’s currency. Fours records them for records an AWS sync has processed since it began recording AWS credits.

Order partner fee details

Google’s reports sometimes let Fours confirm a GCP partner fee only for a group of charges — one order, private offer, SKU, and billing account in one report month — and not for each invoice in it. Fours then shows no fee on an invoice whose own fee it can’t confirm, and View order partner fee on that invoice (or At order level on Cash & Disbursements) opens Order partner fee details, a total for the group that is not the fee of any single disbursement:

  • Confirmed order partner fee — the group’s total from Google’s Detailed Disbursements report, or Unavailable.
  • A coverage badge: Complete source coverage, Partial coverage, or Unknown coverage. Anything but complete adds Source evidence or related invoice coverage is incomplete.
  • Reporting period, Currency, and Evidence (Detailed Disbursements report); the Source order and SKU; and the Group reference.
  • A table of the group’s invoices: Invoice, Invoice amount, Partner fee — or Not available per line — and Disbursement references and dates (Received or Expected with a date, or Date unavailable).

Fours shows the total only when every report row behind the group carries a valid fee, the charges match Google’s Charges and Usage report, and the matched revenue records agree with Google’s figures. If the group can’t be loaded, the dialog reads Order partner fee unavailable. The group’s total is exported once, in the GCP Order Partner Fees report; invoice and payout exports leave the individual fee empty.

Tax on the invoice detail

Most channels show a single Tax amount on the invoice detail. AWS is the exception — an AWS invoice shows two tax lines, because AWS splits who is responsible for remitting the tax:

LineMeaningCounted in the invoice and collectable amounts?
Tax collected & remitted by marketplaceAWS collected this tax from the buyer and remits it to the tax authority itself.No — informational only.
Tax collected & remitted by sellerTax AWS collects and disburses to you; you are responsible for remitting it onward.Yes — it is included in the invoice amount and in the collectable amount. It is not deducted.

Read the two lines together before reconciling an AWS invoice: only the seller-remitted line is cash that passes through your hands — and because it is already inside the collectable amount, do not subtract it again. On an invoice from Fours’ own invoice records that no single revenue record matches, the seller-remitted line shows — instead of an amount (see the caution above).

There is a third AWS tax figure, and it is not on either of those lines. When AWS charges VAT on its own listing fee, the invoice’s marketplace fee carries an incl. $X fee VAT note breaking that amount out. This is tax charged to you on AWS’s fee, not tax on the buyer’s purchase — it is broken out so it can be claimed as recoverable input VAT.

An AWS invoice detail — the Financials panel showing the invoice amount, marketplace fee and collectable amount, followed by the two AWS-only tax lines: tax collected and remitted by the marketplace, and tax collected and remitted by the seller

To check that the tax on your marketplace sales is actually recorded in Avalara, use Tax.

Download an invoice statement

Any invoice in the list can be saved as a PDF marketplace invoice statement for your books: the invoice’s billing, contract, financial, settlement, and refund details on an A4 page, built from the marketplace settlement data Fours holds. It is a bookkeeping statement, not a tax invoice issued by the marketplace.

  1. Select the Download PDF icon on the invoice’s row — or, with the invoice open, Download PDF beside View raw payload.
  2. Check the preview in the Download PDF — invoice ID dialog.
  3. Select Download PDF. The file is saved as invoice-<invoice ID>.pdf, and the dialog confirms Saved invoice-<invoice ID>.pdf.
Statement sectionWhat it holds
HeaderYour organization, the channel, and the invoice status, then the Invoice amount, Partner fee, and Collectable totals.
BillingBuyer, then — when the buyer has completed your sign-up page for one of the invoice’s entitlements — Signed up by: the name, email, and date of the first such sign-up. Then invoice ID, channel, billing entity, issue date, due date (Expected payout for GCP), payment terms, and currency.
ContractProduct, offer, entitlement, service period, CRM opportunity and deal, and reseller.
FinancialsInvoice amount, amount paid, balance due, seller amount due, partner fee and partner fee %, collectable amount, and the tax — on AWS the two lines described above, elsewhere a single Tax amount. On GCP, any amount Google reported as withheld, released, or abandoned. An amount Fours does not know reads —.
SettlementOnly when the invoice has settlement data: the expected and disbursed dates, disbursed amount, bank trace ID, and the disbursement reference — or, for Azure and Stripe, the payment ID.
Refund and credit activityOnly when there is one: the refund’s amount, status, and date, or the write-off.

An AWS statement also notes the listing fee AWS kept from the payout, with any VAT on that fee broken out. On a voided or written-off invoice, the partner fee and collectable amount read —. For an invoice from Fours’ own invoice records, the statement takes the tax, settlement, and refund details from the invoice’s revenue record, AWS sibling rows combined; when no single record matches, they read —. The footer shows when the channel data was last updated.

Anyone who can read Revenue can download a statement, from the Invoices page or from the Invoices tab of an entitlement or buyer. If the PDF can’t be prepared, Fours shows Couldn’t prepare the PDF. Try again.

Saved view

The Invoices page’s views are listed in the rail under Saved views · Invoices — see Saved views for saving, sharing, and who can change a view. A view here keeps the Channel filter, the search, the status and aging filters, the issue-date range (a preset or custom dates), a selected summary card, and the invoice table’s columns and their order. It does not keep the sort. Opening an invoice keeps the view open, and Back to invoices returns to it.

Without a view, only the columns are remembered between visits; the search, filters, date range, and a selected card reset when you leave the page.

KPI calculation formulas

The table keeps every amount in its invoice’s own currency. The cards and the aging chart work in US dollars: each invoice is converted with the rate stored on its matching revenue records, when they are converted to USD, otherwise with Fours’ daily exchange rate from on or before the invoice date (an invoice whose records carry different rates is converted record by record). An invoice whose seller amount due can’t be converted counts as an unknown balance, and one whose amount can’t be converted is left out of DSO. The list combines the invoices Fours holds with revenue records that have no matching invoice — Stripe, Oracle, and Snowflake included — and AWS sibling rows are aggregated into one invoice, by invoice ID and currency, first. The cards cover all of them, whatever the table’s date range, narrowed only by the channel. A revenue record whose invoice amount is negative — a refund or reversal row — is never listed as an invoice, and a listed invoice’s collectable and disbursed amounts are never below zero or above its original invoice amount, before refunds.

KPIApplies toFormulaCalculation details
Total OutstandingAWS, Azure, GCP, Stripe, Oracle, SnowflakeΣ USD seller amount due of open invoicesOpen = seller amount due above zero and not a draft, voided, or written off. When any such invoice in scope has an unknown seller amount due — or one that can’t be converted to USD — the card shows the sum of the known ones, labelled Known balances only; it reads — when none is known. See Seller amount due below.
DSOAWS, Azure, GCP, Stripe, Oracle, Snowflake(Σ USD seller amount due ÷ Σ USD invoice total) × 90, over the invoices whose two amounts are both knownEvery invoice listed counts — any date and any status except draft, voided, and written off, paid invoices included — once its seller amount due and its total are both known in USD. Rounded to two decimals; 0 when those totals add up to zero. Labelled Known balances only while any invoice is left out; reads — (Unavailable: incomplete balances) when none qualifies.
At Risk (90+)AWS, Azure, GCP, Stripe, Oracle, SnowflakeΣ USD seller amount due in the Over 90 bucketThe same open invoices as Total Outstanding; invoices with an unknown balance are left out.
Open InvoicesAWS, Azure, GCP, Stripe, Oracle, Snowflakecount(open invoices) + count(invoices with an unknown balance)An invoice whose seller amount due can’t be converted to USD counts as unknown. Drafts, voided, and written-off invoices are never counted.
Aging bucketAWS, Azure, GCP, Stripe, Oracle, Snowflakebucketed by whole days since the due dateOnly invoices with a known USD seller amount due above zero, excluding drafts. Buckets: Current (not yet due, or no due date), 1–30, 31–60, 61–90, Over 90. Computed at read time against today’s date, the same way for every counterparty; a bucket already stored on the invoice takes precedence. On GCP the due date is the expected payout date.
Net invoiced (Invoice chain)AWS onlyoriginal invoice amount − Σ credit memos + replacement invoice amountThe lines of the Invoice chain, each in the invoice’s own currency; rounded to cents. Shown only on an AWS invoice with a chain.

Seller amount due

The seller amount due — the table’s Seller Amount Due column — is what is still owed to you on an invoice after marketplace fees and confirmed payouts. Every channel reads 0 once the invoice is voided or written off. An invoice from Fours’ own invoice records owes its recorded amount due, and nothing once it is paid — unless it is an AWS, Azure, or GCP invoice that a revenue record matches, in which case the formula for that channel below applies. A revenue record with no matching invoice owes:

Channel partnerFormulaIncluded/excluded dataDate, currency, and rounding rules
AWScollectable amount − net amount collectedNet amount collected = what AWS’s billing-event ledger shows it collected after its fee, or the disbursed amount when that is larger. The collectable amount already reflects the refunds AWS applied, so refunds are not subtracted again. A record marked paid or collected with nothing collected owes 0.In the record’s own currency, unconverted; never below zero.
Stripethe amount Stripe reports as remaining on the invoice0 once Stripe marks the invoice paid. Unknown when Stripe’s remaining amount was not recorded. A Stripe invoice imported into Fours’ own invoice records owes Stripe's amount due − amount paid. An older Stripe bill that Fours issued and that stored its amount only in the bill’s details owes that amount less its successful Stripe charges; with no successful charge, its amount paid is a known 0.Stripe’s own amounts, in the invoice currency.
Azurecollectable amount − disbursed amountNo refund is subtracted. Unknown when the collectable amount reads 0 with no channel fee to explain it. An Azure invoice from Fours’ own invoice records that no revenue record matches is unknown.Record currency; never below zero.
GCP(collectable amount − GCP refund) − the larger of payouts already due and the collected amountA payout counts only once its expected payout date — the 21st of the month after its report month — has passed; when Google pays a charge across several monthly reports, each report’s payout counts on its own date. Settled month: once the expected payout date has passed, an invoice owes 0 when Google’s reports show its whole month settled for that Google entity and currency — the month’s amounts due to you in the Charges and Usage report add up to the month’s Detailed Disbursements total, with nothing negative, withheld, released, abandoned, or deducted for refunds — and the invoice’s own charge and amount due match Google’s rows, even when the payout can’t be tied to single invoices. Otherwise unknown when the collectable amount reads 0 with nothing to explain it (a zero invoice total, a fee Google’s reports confirm equals the whole fee base, or a channel fee equal to the invoice amount less any prepay credit), the refund amount is incomplete, Google deducted a refund from that month’s payout, or a payout is negative. A GCP invoice from Fours’ own invoice records that no revenue record matches is unknown.Record currency; never below zero. Days overdue count from the expected payout date.
Oracle, Snowflake(collectable amount, else invoice amount) − refund − amount collectedRefund = the refund invoice amount recorded on the record, when the refund applies. Amount collected = the larger of the collected and disbursed amounts. 0 once the record is marked paid.Record currency; never below zero.

Balance due

Amount paid and Balance due describe the buyer’s side of the invoice, gross of marketplace fees. They appear in the invoice detail, the PDF statement, and the reports; the cards and aging do not use them.

Channel partnerAmount paidBalance due
AWSΣ seller revenue share + seller tax share of AWS's COLLECTED events — the buyer’s gross payments, before fees and refunds (see AWS collection below). On an invoice built from a revenue record with no collected seller revenue share, it falls back to 0 when a refund applies, else the invoice total once the record is paid, else the smaller of the total and the larger of the collected and disbursed amounts. A matched invoice from Fours’ own invoice records keeps its stored paymentinvoice gross − refunds that apply − amount paid, never below zero; 0 once written off or voided
StripeThe amount Stripe reports as paid — else the collected amount, else the payout of a paid recordThe same as the seller amount due
Azure, GCP— on an invoice built from a revenue record, because the channel reports what it pays you, not what the buyer paid. On an invoice from Fours’ own invoice records, the stored amount paid when it is above zero; a stored zero only when the invoice total is above zero and amount paid plus amount due equals it— on an invoice built from a revenue record. On an invoice from Fours’ own invoice records, the stored amount due when it is above zero; a stored zero only when the invoice total is above zero and amount paid plus amount due equals it, or the invoice is marked paid. 0 once voided or written off
Oracle, Snowflakeinvoice total − refund once the record is marked paid, otherwise the smaller of that and the amount collectedThe same as the seller amount due

AWS collection. For AWS, the amount paid comes from the COLLECTED events in AWS’s billing event data feed — AWS’s record of the amount it collected from the buyer. Fours counts every such event, including one AWS marks as not balance-impacting (shown for information, with no effect on your disbursement balance), and adds the seller revenue share and the seller tax share they carry; the latest event’s date is the collection date. Because that is the buyer’s gross payment, fees and refunds are not taken off it. An AWS invoice can therefore read Paid or Partially Paid before its payout arrives.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.