Every period someone works down the vendor list. Who billed, who didn't, and what should have come in. On a small team that review eats a day, and the cutoff test eats another as last month's invoices keep arriving.
What Flux Runs Each Period
- Accrual schedule with reasoning per vendor. Each line shows the method and the evidence behind it: a bill received after period end, a PO and receipt, timesheets, or run-rate.
- Missing-bill list. Recurring vendors whose usual bill hasn't shown up, checked against six to twelve months of AP history.
- Cutoff test. Bills entered after period end with service dates inside it, flagged for accrual.
- Proposed journal entries. Debit the expense account, credit accrued liabilities, reverse on day one of next period.
- True-up of last period. Each reversed accrual matched to the actual bill, with the difference shown.
- Open-questions list. Items the files can't answer, like a legal bill with no hours or a contract we haven't seen.
What Your Team Keeps
- Approving or changing every proposed accrual before it posts.
- The estimates that need judgment: bonuses, disputed bills, part-done fixed-fee projects.
- Whether a small item clears your materiality threshold.
- Posting the entries in your ledger.
What We Need From You
| Item | Detail |
|---|---|
| AP bill history | Six to twelve months by vendor, exported from QuickBooks, NetSuite, Sage Intacct or Xero |
| Bills received after period end | The AP register for the first 10 to 15 days of the new month |
| Open POs and receipts | Only if you use purchase orders |
| Trial balance | Period end, so every accrual ties to the ledger |
| Last period's accrual schedule | To run the true-up and keep your layout |
| Known changes | A short note on new contracts, cancelled vendors or price increases |
| Time from you | About 30 minutes to send files, then 1 to 2 hours to review |
What You Get Back
You get the accrual schedule, proposed entries and open questions in a workbook laid out like yours. For the free run on a closed period, that arrives within one business day of complete files. Amounts tie to the trial balance before any reasoning is written. In one recent engagement at a US$10M online business run by one controller, accruals proposed from vendor history took the quarter-end close from 8 days to 5. Figures approximate.
What It Looks Like
Illustrative, with sample numbers, not a client engagement.
A software vendor's last six bills average US$4,210, and the March bill hasn't arrived by April 8. The schedule proposes US$4,210 on run-rate and says so. A contractor's timesheet shows 32 hours at US$150, so that line is US$4,800 with the timesheet cited. The outside law firm sent no bill and no hours, so it goes on the questions list instead. Don't accrue legal fees on run-rate.
Common Questions
Do you post entries in our ledger?
No. We work from files you choose to send, with no system access. You get proposed entries with support, and your team posts them.
What if a vendor has no history?
It goes on the open-questions list with what we'd need to estimate it. We don't put a number on a vendor with no evidence.
How do we check your accruals against ours?
The free run uses a period you've already closed. Put our schedule next to yours and compare it line by line. Where they differ, the reasoning column shows what we used and what we didn't have.