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. 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

Card	Meaning
Total Outstanding	Sum of unpaid invoice balances, excluding paid, voided, and written-off invoices.
DSO	Days Sales Outstanding — total outstanding as a share of everything invoiced, expressed in days.
At Risk (90+)	Outstanding balance in the oldest aging bucket.
Open Invoices	Count of invoices with a remaining balance due.

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).

The cards add each invoice’s balance in its own currency without converting it, and show the total in dollars — so when your invoices span more than one currency, the total mixes them.

Aging buckets

The aging chart splits outstanding balances into Current, 1–30, 31–60, 61–90, and Over 90 days. An invoice is included while it is open — anything not paid, 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 and its aging bucket), not the bucket-level totals.

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 %), balance 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. 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 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, 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, unless it is a draft, voided, or written off; an invoice built from a revenue record never takes that status. 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.

To inspect a single invoice:

Find the invoice in the table — use search or the status/date/channel filters to narrow the list.
Select View Details on its row.
Review the record — billing and contract terms, financials, and settlement — alongside a lifecycle timeline (issued → payment applied → disbursed/swept → written off).
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.

Caution

Some invoice-detail fields depend on where the invoice comes from. An invoice built from a revenue record — one with no matching invoice in Fours’ own invoice records — can show the refund amount and date and the payment, bank-trace, and disbursement references from that record, and on AWS the marketplace and seller tax split and the incl. $X fee VAT note, when the channel supplied them. An invoice from Fours’ own invoice records takes those details — and its collectable and disbursed amounts — from the one revenue record that matches it on channel, currency, and invoice ID, AWS sibling rows combined. When no single record matches, it shows none of those details, and its seller-remitted tax line shows —. It shows a Disbursed step only once that record has an actual disburse date, and its dunning history when it has one. Neither kind fills in the refund status, the write-off details, or the earning ID at the moment. Revenue Records and Cash & Disbursements carry the underlying tax, refund, and payout references, and the PDF statement takes its tax, settlement, and refund details from the same revenue record.

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 balance due, amount paid, and aging bucket beside them:

Invoice detail header with status and amount circled

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:

Line	Meaning	Counted in the invoice and collectable amounts?
Tax collected & remitted by marketplace	AWS collected this tax from the buyer and remits it to the tax authority itself.	No — informational only.
Tax collected & remitted by seller	Tax 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, 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.

Select the Download PDF icon on the invoice’s row — or, with the invoice open, Download PDF beside View raw payload.
Check the preview in the Download PDF — invoice ID dialog.
Select Download PDF. The file is saved as invoice-<invoice ID>.pdf, and the dialog confirms Saved invoice-<invoice ID>.pdf.

Statement section	What it holds
Header	Your organization, the channel, and the invoice status, then the Invoice amount, Partner fee, and Collectable totals.
Billing	Buyer, invoice ID, channel, billing entity, issue date, due date (Expected payout for GCP), payment terms, and currency.
Contract	Product, offer, entitlement, service period, CRM opportunity and deal, and reseller.
Financials	Invoice amount, amount paid, balance due, partner fee and partner fee %, collectable amount, and the tax — on AWS the two lines described above, elsewhere a single Tax amount.
Settlement	Only 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 activity	Only 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.

KPI calculation formulas

Every amount stays in its invoice’s own currency; the cards add them without converting. 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.

KPI	Applies to	Formula	Calculation details
Total Outstanding	AWS, Azure, GCP, Stripe, Oracle, Snowflake	`Σ balance due of open invoices`	Open = balance due above zero and not voided or written off. See Balance due below.
DSO	AWS, Azure, GCP, Stripe, Oracle, Snowflake	`(total outstanding ÷ Σ total of every invoice) × 90`	The denominator is the total amount of every invoice listed — any date and any status, including paid, voided, and written-off ones. Rounded to two decimals; 0 when there are no invoices.
At Risk (90+)	AWS, Azure, GCP, Stripe, Oracle, Snowflake	`Σ balance due in the Over 90 bucket`	The same open invoices as Total Outstanding.
Open Invoices	AWS, Azure, GCP, Stripe, Oracle, Snowflake	`count(open invoices)`	Open = balance due above zero and not voided or written off.
Aging bucket	AWS, Azure, GCP, Stripe, Oracle, Snowflake	bucketed by `whole days since the due date`	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.

Balance due

An invoice from Fours’ own invoice records owes its recorded amount due, and nothing once it is paid, voided, or written off. A revenue record with no matching invoice owes the amount below, never less than zero — and nothing once it is marked paid, voided, or written off:

Channel partner	Formula	Included/excluded data	Date, currency, and rounding rules
AWS	`collectable amount − refund − amount paid`	Refund = the refund invoice amount recorded on the record, whatever the refund’s status. Amount paid = the larger of the collected and disbursed amounts.	In the record’s own currency, unconverted; totals rounded to cents.
Azure, Stripe, Oracle, Snowflake	`(collectable amount, else invoice amount, else disburse amount) − refund − amount paid`	The same refund and amount-paid rules as AWS.	Same as AWS.
GCP	`(collectable amount, else invoice amount, else disburse amount) − refund`, until the record is paid	The same refund rule as AWS. A payout amount Google reports is not counted as paid: GCP records carry no collected amount, so amount paid stays 0 through the expected payout date. After that date, a record is paid in full — balance due 0 — once Google has reported a non-zero payout amount, a negative clawback included; without one it stays due and reads Overdue. An older record with no expected payout date counts as paid once it has a disburse date.	Same as AWS; days overdue count from the expected payout date.

AWS collection. For AWS, the collected amount 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); the collected amount is their total, and the latest event’s date is the collection date. 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.