For Accounting
A cleaner close. Nothing posts without you.
The close is days of pulling evidence, building accruals and chasing approvals. Sebastian prepares the work from the records. You check it and approve it. The ERP stays the system of record.
In the product
How accounting uses Sebastian
Debit, credit, the calculation and the evidence. You verify it and approve it. Nothing posts until you do.
Journal review · drafted by Sebastian
Proposed cloud expense accrual
AccountDebitCreditCloud expense 6120 · COGS$30,000—Accrued liabilities 2150—$30,000
Reasoning
AWS usage through 19 October comes to $440,000 at the current provider rates. $410,000 is posted in the ledger. The $30,000 difference has been incurred and is not yet recorded, so it belongs in October under the accrual policy.
Sources
AWS usage report
NetSuite GL entriesPolicy §4.2
AWS usage reportNetSuite GL entriesPolicy §4.2Approve and post to ERPRequest changes
Tomás reviews by Thursday. Nothing posts until a person approves it.
Before and after
Your close, before and after
| Aspect | Status quo | Sebastian |
|---|---|---|
| Preparing an accrual | Usage export, rate card, spreadsheet, email. | Drafted with the calculation and evidence. You verify and approve. |
| Invoice exceptions | A flag in AP and a thread with procurement. | Purchase order, receipt and invoice side by side, the difference named. |
| Revenue treatment | A memo, a workbook, and a debate with FP&A. | Three schedules on the contract, the clause cited, both versions kept. |
| The audit trail | Rebuilt from email when the auditors arrive. | On every entry from the start. |
Related