Skip to main content
Now in beta, Request early access →
GL Reconciliation

Reconcile every schedule without the month-end scramble.

Voltra imports your GL transactions and surfaces them as reconciliation schedules your controller can actually work. Build the rules once, run the engine, and see what cleared and what is still open, with notes and history on every item. Your GL stays in your accounting system. Voltra reads from it and never writes back.

Month-end is a race against incomplete schedules

Every controller knows the feeling. The GL has hundreds of line items. Accounts sit in the wrong department, schedules are half-built in a spreadsheet someone started three months ago and never finished. Open items fall through the cracks and surface six weeks later as a journal entry nobody can explain.

It does not have to work that way. Voltra gives your accounting team one place to see every schedule, work every open item, and keep a permanent note trail, without touching the GL itself.

GL transactions come in, you reconcile on top

Voltra imports GL transactions from your DMS. Those transactions are read-only inside Voltra because your accounting system is and stays the source of truth for the GL. What Voltra adds on top is the reconciliation layer: schedule views, rule-based matching, open-item notes, and account classification, all of which live in Voltra and are owned by your team. If you run Cash-in-Transit in GL-funded mode, deal status in that module is derived directly from the GL import, which means your CIT and your schedules stay in sync without any manual bridging.

Voltra does not post journal entries

GL transactions are imported into Voltra for reconciliation purposes only. Voltra does not create, edit, or delete transactions in your accounting system. The GL stays exactly as your accounting team left it.

Build rules so the engine does the matching

The reconciliation engine in Voltra runs against rules your team defines. Six comparison types give you precise control over how items match across the GL and your other source data. Group related rules together to keep your reconciliation logic organized. When you run the engine, it applies every rule and surfaces what cleared automatically, so your controller is only looking at the exceptions.

The rules and rule groups are stored in Voltra. They are your reconciliation logic, and for that, Voltra is the system of record.

Work open items and keep the note history

Every open item on a schedule has a notes field. Attach a note explaining what the item is, what is being investigated, or why it is waiting on something else. Notes are timestamped and attributed. When month-end hits, the audit trail is already there because the work was documented in real time rather than reconstructed afterward.

A controller coming in mid-month can open any item and see exactly what has been done. No more "who touched this?" on a Friday afternoon.

The notes live in Voltra, the GL does not

Schedule notes are owned by Voltra. They are not written back to the DMS or accounting system. The note history stays permanently attached to the open item, visible to anyone with accounting access.

Configure which accounts show and how they are classified

Not every GL account belongs on every schedule. Voltra lets you configure which accounts feed each schedule view, so the controller sees the right slice without scrolling through hundreds of unrelated lines.

You can also override the statement-group and department classification for any account directly in Voltra. If the DMS has an account parked in the wrong department for your reporting needs, you fix the classification here, not in the accounting system. The override stays in Voltra and applies whenever that account appears in a schedule.

The right people reconcile, scoped by role

GL reconciliation in Voltra is scoped to the roles that need it. Accounting and controller roles have access; other roles do not see the module. At a group with multiple locations, access follows the location scope on each user's profile, so a controller at one store does not accidentally work another store's schedules.

Accounting
Works open items, attaches notes, runs the reconciliation engine.
Controller
Builds and maintains rules, configures account classification, reviews results.
GM / Owner
Cross-location view of schedule status with appropriate role permissions.

Sits on top of your accounting system. Never writes back.

Voltra reads GL transactions from your DMS and surfaces them for reconciliation. That is the full extent of the connection to your accounting system. Voltra does not post to the GL, does not create or edit transactions, and does not touch anything in your DMS. Your accounting system stays your system of record for the GL. Voltra is where your team does the reconciliation work on top of it.

For details on how Voltra connects to your existing systems, see multi-source integration. If you process F&I product remittances, the F&I remittance module sits in the same accounting workflow and closes the loop between back-office cost and provider statements. To see the full set of operational modules, start at all features.

Common questions about GL reconciliation

Voltra imports your GL transactions from the DMS and surfaces them as reconciliation schedules. You build rules that define how items match (six comparison types), run the reconciliation engine, and review the results. Open items that do not match a rule stay visible until they clear. Your GL stays in your accounting system; Voltra is where the reconciliation work happens.

Open schedule items show in Voltra as soon as they come in from the GL import. You attach notes directly to each open item, explaining what it is, what is being done, or why it is still open. That note history is saved in Voltra, so any controller who looks at the item later can see exactly what was done and when.

In Voltra, you create reconciliation rules using six comparison types and organize them into rule groups. When you run the reconciliation engine, it applies those rules against the imported GL transactions and surfaces what cleared, what is still open, and what needs review. The rules live in Voltra; they are the system of record for how your reconciliation logic works.

No. Voltra reads your GL transactions from the DMS; it does not post to it, edit it, or replace it. Your accounting system stays the system of record for the GL. Voltra is where you run the reconciliation work on top of those imported transactions. It reads from your systems and never writes back to them.

Voltra lets you configure which GL accounts appear in each schedule. You can also override the statement-group and department classification for any GL account, so the schedule surfaces the right view for your controller without touching anything in the accounting system.

Attach notes directly to open schedule items in Voltra. Every note is timestamped and attributed to the person who wrote it, so the full history of what was worked, flagged, or resolved stays tied to the item. When month-end comes, your audit trail is already there.

Accounting and controller roles have access to the GL reconciliation module in Voltra. Access is scoped by role and location, so each team member sees the schedules that are relevant to them. The GM or controller can see across locations if their role allows it.

See your schedules reconciled, not rebuilt.

Free walkthrough using sample data shaped like your store. We will show what GL reconciliation looks like on the systems you already use.

Get a Demo All Features

Free · 15 minutes · No commitment · Talk to someone who's run a dealership