This workflow ensures invoices are captured, validated, and routed correctly without manual double-entry. It solves the common issues of lost invoices, mismatched GL codes, and over-budget approvals by combining OCR automation with clear user checkpoints. The result is faster processing, fewer errors, and accurate budget tracking.
This guide explains how invoices are processed using OCR and AI. There are two types of invoices you may encounter:
Single-period invoices (cover only one month)
Multi-period invoices (cover more than one month, require Prepayment Configuration)
Use this if you want to process a vendor invoice.
Vendors send invoices to the designated company email address.
The system automatically detects the email and processes the attached invoice.
What happens next
The invoice attachment is queued for OCR extraction.
Use this to capture basic invoice details.
The system scans the invoice and extracts:
Vendor
Invoice number
Invoice and due dates
Service period
Line items, descriptions, and amounts
What happens next
Extracted data is saved into a new task.
OCR only captures data. It does not assign GL codes.
Use this to assign the right GL code to each line item.
A knowledge and AI learning layer automatically assigns GL codes.
Mapping is based on:
Historical invoice patterns
Vendor and description context
Continuous learning from user corrections
Stored budget [table] categories (e.g., fixed vs variable costs, property vs HQ allocations)
GL Code Assignment Rules
The system evaluates each line item against historical mappings for the same vendor or description.
If a clear match exists, the same GL code is applied.
If multiple possible GL codes exist, the system uses context (invoice description, category keywords, budget classification) to suggest the most likely code.
If confident found is less than 85%, then no automated gl code mapping, and the task is flagged for review.
Every user correction feeds back into the learning model for future accuracy.
GL-Based Approval & Assignment Rules
Once a GL code is assigned, approval routing is determined by the code:
Property Manager → operational categories (e.g., cleaning, waste, pest control)
Facilities Team → infrastructure/system categories (e.g., HVAC, lifts, fire safety)
HQ Direct → specified categories requiring central finance approval (dependent on GL code mapping)
What happens next
GL codes are suggested for each line item.
You must review and confirm them.
Any corrections improve future accuracy.
Use this to confirm details before approval.
Open the task.
Review extracted invoice data.
Check AI-assigned GL codes and descriptions.
What happens next
Task remains open until approved.
Important: Avoid adding multiple line items with the same GL code.
Use this to confirm whether the invoice is within budget.
The system compares invoice line items against stored budget files.
What happens next
Month-to-Date (MTD) check: flags if this month’s spending for the GL code is over budget.
Year-to-Date (YTD) check: flags if annual spending for the GL code is over budget.
If flagged, additional approval may be required.
Use this when an invoice covers more than one month.
Open the invoice line item.
Complete the Prepayment Configuration form (GL code, service period, recognition method).
Save the configuration.
What happens next
All recognition entries (past, current, and future) are generated instantly.
Values are fixed and evenly distributed.
Reporting remains accurate without timing errors.
Examples
$8,000 subscription (12 months) → 12 entries of $667 each.
$3,000 service (3 months) → 3 entries of $1,000 each.
Use this to finalize invoice processing.
Review all details.
Approve the task.
What happens next
GL postings update using AI-mapped codes.
Budget vs actual reports update in real time.
Prepayment recognition entries (for all periods) are already in place.
If you want to… | What to do | Result | Example |
|---|---|---|---|
Process a single-period invoice | Review OCR + AI GL codes → approve | Invoice posted once; budget reports update in real time | $2,500 utility bill (March) |
Process a multi-period invoice | Use Prepayment Configuration → save → approve | All recognition entries created instantly; values evenly distributed | $12,000 annual license → 12 × $1,000 |
Check | What it does | Result |
|---|---|---|
MTD | Compares monthly spend for GL code against monthly budget | Flags task if exceeded |
YTD | Compares yearly spend for GL code against annual budget | Flags task if exceeded |
OCR extracts data; AI assigns GL codes.
Always review GL codes before approving.
System continuously checks invoices against stored budget files.
Prepayment instantly generates recognition entries for past, current, and future periods.
Do not duplicate GL codes across line items.