Short answer
“Review required” means Balansix has enough information to assist with coding but not enough accounting authority to post the row automatically with confidence.
What to check first
Why this happens
Balansix separates routine automation from professional judgement. A suggestion can be useful without being safe to post automatically, particularly where VAT, settlements or ambiguous descriptions are involved.
Steps to resolve it
- Open the row and inspect the proposed coding.
- Add or select the correct accounting destination.
- Confirm VAT treatment only where the bank line is the appropriate source under the client’s accounting mode.
- If the row pays an invoice, use settlement matching instead of coding it as a new expense or income item.
- Save/approve the row so it can move to the ready-to-post state.
What to avoid
Frequently asked questions
Is Review required an error?
No. It is a workflow state indicating that a user decision is required before posting.
Can I post several reviewed rows together?
Where the rows have reached the appropriate ready-to-post state, Balansix can support efficient batch processing while preserving row-level accounting detail.
Why does VAT make a bank row require review?
The correct VAT treatment can depend on whether the bank line or an underlying source document is authoritative, so an automatic guess may be inappropriate.