Reporting & Reconciliation

Find payment mismatches in one place

Compare ledger entries, provider payments, and statement rows. See what matches, what is missing, and what finance needs to review.

Reference matchingAmount checksMissing recordsReview history

Talk through your data sources See the match results

Available data sources and accounting connections are confirmed during setup.

Bring the three sides of a payment together

Instead of checking each source in a separate tab or spreadsheet, compare the key fields for the same period in one view.

Ledger entries

Use the invoice or journal reference, account, amount, currency, and date recorded in your ledger.

Provider payments

Compare the payment ID, status, amount, currency, and payment date returned by the connected provider.

Statement rows

Add the statement reference, amount, currency, fee, transaction date, and original description.

See exactly where records disagree

Strong references are checked first. If a payment is missing or the values differ, Gruv leaves it open for review instead of treating it as complete.

Match

The reference, amount, and currency line up.

Amount differs

The references connect the records, but the amounts do not agree.

Missing from provider

A ledger entry has no matching payment in the provider data.

Missing from ledger

A provider payment or statement row has no matching ledger entry.

Possible match

The amount and account look related, but finance needs to confirm the match.

Keep the answer with the mismatch

A mismatch needs more than a red cell in a spreadsheet. Keep the references, supporting information, next step, and final answer together so finance can pick up where the last reviewer left off.

What finance can see

Issue type and current status
Provider and account context
Invoice, provider, and journal references
When the issue first and last appeared
Confidence and supporting information
Suggested next step and final resolution

Set up the review around your data

Start with the sources finance already uses. Then decide how to match them, who reviews each type of issue, and where the result goes next.

Connect the sources

Choose the provider records, statement files, accounts, and currencies finance will compare.

Map the IDs

Identify the payment, invoice, journal, and statement references that connect the same transaction.

Set the review rules

Agree on amount tolerances, the review window, when a possible match needs confirmation, and who owns each issue.

Choose the next handoff

Keep the result in the review flow, export it for finance, or connect it to an accounting workflow set up for your team.

Connect reconciliation to the rest of finance

The same payment may also appear in a payout batch, an FX conversion, or an integration. Review those workflows when you decide which references finance needs.

Mass payouts FX conversion Integrations

Frequently Asked Questions

What can Gruv compare?+

Gruv can compare the ledger entries, provider payment records, and statement rows connected for your account. The sources available to your team depend on the provider and statement feed set up for your program.

How does Gruv find a match?+

Gruv looks for a shared provider, invoice, or journal reference first. It then checks the amount and currency. When the references or values do not line up, the payment is sent for review instead of being marked as settled.

What kinds of mismatches can finance see?+

Finance can see amount differences, ledger entries missing from the provider data, provider or statement records missing from the ledger, and possible matches that need confirmation.

What stays with a review item?+

The issue type, status, account context, invoice, provider and journal references, first- and last-seen times, supporting information, suggested next step, and final resolution can stay together.

Does reconciliation send results to our accounting system?+

That is a separate setup decision. Confirm the destination, fields, review step, and posting approach before sending reviewed results downstream.

Bring us one sample period

Share a sample ledger export, provider records, and statement format. We'll map how matches and mismatches should appear, who reviews them, and what finance needs next.

Talk through your data sources