Accruals built from actual deliveries
Received-not-invoiced is a report of real goods receipts against open purchase orders. That is the difference between an accrual you can explain line by line and one you can only justify.
Receipts arrive when the card is paid, recurring invoices are fetched on schedule, and each entry posts with its document and approval attached.
Start the close before the month ends
Entries post as transactions happen, already coded and supported, which makes the last day of the month the day you stop working on the period instead of the day you start.
- Continuous posting, with no month-end batch
- Reconciling items aged and stale ones flagged
- Close status visible for each entity
Every entry keeps its own support
The receipt, invoice or bank advice sits on the transaction alongside the approval chain. Corrections go in as reversing entries, never as edits. The audit trail holds up when someone pulls on it.
- Document attached to the transaction itself
- Approval chain kept with approver and timestamp
- Corrections posted as reversals, never as edits
Why teams switch
The close starts with chasing documents that already exist.
The first week of every month goes to chasing documents that already exist somewhere.
Receipts come from the stores that send them at the moment of payment and recurring invoices are fetched from the vendor on a schedule, which leaves you chasing only the documents that were genuinely never issued.
Accruals get built from run-rates because nobody records a delivery until the end of the week.
Goods are receipted against the purchase order when they arrive. The received-not-invoiced balance is a list of actual deliveries a reviewer can tick through.
The auditor asks for the invoice behind one number and it takes half a day to find it.
The document sits on the transaction record with its approval chain. Getting from a reported figure to its support takes one click and never leaves the system.
The products that do the work.
Each product works on its own, and when you run two, the same record carries from the receipt to the ledger entry.
Accounting automation
Accounting automation software that codes each transaction and posts the journal entry to your accounting software the day it happens.
Accounts payable
Accounts payable automation that reads each supplier invoice, codes it and matches it to the purchase order before anyone is asked to approve payment.
Expense management
Capture receipts, categorize expenses and check policy compliance as expenses are submitted.
FAQ
Frequently asked questions
What people ask us before they sign up.
The days that shrink are the ones spent waiting for documents to arrive, which for most teams is most of the elapsed time but not most of the work. Reconciliations, judgement calls and review still take as long as they take, and we'd rather set that expectation before you buy than after.
No. Your general ledger stays where it is and remains the system of record. Smartbills sits in front of it and posts coded entries into it, each one with its support attached.
They stay with you. Coding rules handle the repetitive volume and send anything ambiguous to a person with the document already attached, which shrinks the queue you have to think about without pretending it's empty.
Yes. Each entity keeps its own currency, chart of accounts and close status, and the entities consolidate without an export step in between.
Get started
Run next month's close in parallel
Put one period through Smartbills alongside your current process and compare the day your numbers were actually ready.