Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
About This Automation
Suspense account clearing is the manual process of identifying, categorizing, and posting unclassified transactions back to the correct general ledger accounts.
Automation analyzes suspense transactions, retrieves supporting documents, and recommends the correct GL code based on transaction details and historical patterns. The bookkeeper reviews and approves recommendations, then posts corrected entries automatically, cutting manual time by 80 percent.
Key features:
Retrieve supporting documents automatically from email and bank feeds for each suspense transaction
Recommend the correct GL code based on transaction details and historical coding patterns
Flag low-confidence matches for human review before posting
Record all coding decisions and audit trails in a centralized log
Post approved journal entries to the general ledger without manual data entry
The issues teams report most often with this process
#
Friction point
Companies Report This
1
Document search across multiple systems
Bookkeepers spend 12 minutes per transaction searching email, bank feeds, and client portals for source documents.
80%
2
Manual GL code selection
Determining the correct GL code requires reviewing the chart of accounts and transaction context for each item.
67%
3
Manual journal entry creation
Bookkeepers must manually create and post journal entries in the accounting system for each cleared transaction.
53%
4
Spreadsheet data entry
Coding decisions must be recorded in a spreadsheet, creating duplicate data entry and audit trail gaps.
40%
5
Month-end close delays
Uncleared suspense accounts delay the close process by one to two days each month.
26%
DisclaimerAll data is based on anonymized FullSpec mapping sessions and proprietary industry research. Learn more
Automation readiness
How well-suited this process is for automation
Process Pain Score™Manual document hunting and coding decisions consume 14+ hours monthly and.
8.2/ 10
AI Fit Rating™Pattern matching and document retrieval are ideal for automation; human review.
8.6/ 10
Automation Lift Index™Automation reduces manual time by 80 percent and eliminates coding errors.
8.2/ 10
Hidden Overhead™Context switching between email, spreadsheet, and accounting system adds.
6.8/ 10
How The Automation Works
The full workflow, from trigger to completion.
Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
1. Suspense Account Balance Detectedtrigger
The automation monitors the suspense account daily and triggers when the balance exceeds zero or at the start of month-end close.
2. Extract Suspense Transactions
The automation pulls the list of uncleared transactions from the accounting system and retrieves transaction metadata including amount, date, and description.
3. Retrieve Source Documents
The automation searches email and bank feeds to locate the original invoice, receipt, or statement that explains each transaction.
4. Match to GL Code
An intelligent analyzes the transaction description, amount, and source document to recommend the correct GL code based on the client's chart of accounts and historical coding patterns.
5. Review Matches for Approval
High-confidence matches are flagged for quick review; low-confidence or unusual matches are held for manual verification by a bookkeeper.
6. Post Approved Entries to GL
Approved matches are automatically posted as journal entries in the accounting system, moving transactions from suspense to the correct GL code.
7. Send Completion Report
The automation sends a summary report to the team showing how many transactions were cleared, how many require manual review, and the updated suspense balance.
Everything you need to know before mapping this process.
Low-confidence matches are flagged and presented to the bookkeeper for manual review and decision before posting. The bookkeeper retains full control over final GL code assignments.