Why is subscription revenue hard to reconcile by hand?
A billing processor pays out in batches that combine many invoices, net of fees, minus refunds and disputes, sometimes across currencies, on a schedule that does not match the invoice dates. Reconstructing which invoices a payout covers at month end is slow, error-prone, and the reason many SaaS closes take weeks. A Finance Controller Digital FTE on ftes.ai does the matching every morning instead, when the processor's records are fresh and the exceptions are few.
The work has a checkable right answer in the processor's own data, which is what makes it a first-month function.
What does a payout match show?
The payout amount and date; the invoices it covers with their amounts; the refunds and disputes deducted; the processing fees, with the fee schedule that explains them; any currency conversion the processor applied; and the ledger entries the FTE proposes to record it. Every line traces to the processor's records through a dedicated, read-scoped connection, and the manager approves the match in seconds or sends it back with a reason. Nothing posts to the ledger until approved.
A payout that does not fully match is proposed as a partial match with the unexplained difference isolated, which is usually a fee change, a dispute, or a timing difference the FTE names.
- Payout: amount, date, currency
- Covered: invoices, refunds, disputes, fees with the schedule
- Proposed: ledger entries, approved before posting
How are failed payments, refunds, and disputes handled?
They surface in the morning brief the day the processor records them, with the customer, the invoice, the amount, and the processor's reason. The FTE proposes the ledger treatment and, where the remit allows, drafts the dunning or confirmation communication for approval. It never decides to refund, never issues a credit, never contests a dispute, and never changes a subscription; those are decisions about money and accounts that stay with the finance lead and the account owner. Recurring failed payments for one customer are flagged as a pattern for the account owner.
The value is timing: a dispute known on the day it is filed is one the company can answer in time.
What does the FTE never do in finance?
It never posts an entry without approval, never decides revenue recognition or tax treatment, never issues refunds or credits, never changes a customer's plan or billing details, and never contacts a customer about money without an approved draft. Its connection to the processor and the ledger is dedicated, read-scoped where the tools allow, encrypted, and revocable in one logged action. Exact matches under a threshold the manager sets can earn autonomy from the record at a monthly review; anything involving a judgement never does.
A qualified person signs the close. The FTE makes the close a review rather than a reconstruction.
How does the close change?
On the first day of the close, the controller opens a ledger where every payout of the month is already matched or proposed, with the exceptions isolated and named. The close is a review of those exceptions and the judgement items, revenue recognition, accruals, deferred revenue, rather than a reconstruction of what the processor did. The measure is days to close and exceptions open on day one against the last two closes, and it is a number the company already tracks.
Most SaaS finance teams find the first close after a full month with the FTE is the first one in a while that started from a matched ledger.
What does the first month look like?
Week one: connect the billing processor and the ledger with dedicated scoped accounts, write the remit with the match threshold and the escalate list, and record the baseline from the last two closes. Weeks two to four: approve evidenced matches each morning in minutes, send back with reasons, and read the reasons weekly; most are fee-schedule or timing rules the remit can absorb. Day 30: read the FTE's own report, run the first close from the matched ledger, and decide whether exact matches under the threshold have earned autonomy.
The honest comparison is at the second close, when a full month ran with the FTE from day one.