Yoga FSM - Statement Matching

 

Table of Contents

What Statement Matching Does
Getting Access
How Statements Get Into Yoga
The Statements Automation View
Statement Statuses
Working a Statement
Automatic Matching
Line Actions
Research Tool
Payment & Receipt Details
Emailing the Vendor
Accruals & Export
Disputes & Notes
Permissions
Reporting
FAQ

What Statement Matching Does  

Vendor statements are one of the last places AP teams still reconcile by hand — opening a PDF or spreadsheet from the vendor, then hunting through AP one invoice number at a time to work out what’s already paid, what’s in process, and what was never received at all.

Statement Matching does that research before anyone opens the statement. When a vendor statement arrives, Yoga identifies the vendor, reads every activity line, and matches each line against your AP data. By the time a reviewer opens the record, matched lines are already linked to their source documents and only the genuine exceptions are left to work.

From there, the statement is a single workspace: accrue what’s missing, ignore what doesn’t apply, research anything ambiguous against your full AP history, and email the vendor a formatted status table without leaving the record.

Note:  “Matching” here means matching statement lines to your AP documents in Yoga. This is not invoice-to-PO or invoice-to-receipt matching in your ERP, and it does not perform three-way match. Receipt and payment details are displayed on matched lines, but the reconciliation itself is statement-to-AP. 

Back to Top

---

Getting Access 

Statement Matching is a separate Yoga solution, not part of the standard invoice automation license.

Licensing. Statement Matching is an addition to your Yoga platform fee. It does not change how your invoice or EDI ingestion is billed. For pricing specific to your organization, contact your Client Success Manager or email YogaSupport@RPIC.com.

Free trial. You can try Statement Matching in your TEST environment with up to 5 statements per calendar month, using your own vendor statements and your own AP data. No rollout request is required to start — Yoga Super Users can begin from the Statement Matching capture page. The counter resets at the start of each calendar month.

Navigate to the Capture: Statement Automation (Free Trial) to upload your Vendor Statement:

And it will open the Drag & Drop Capture Page:

Full enablement. Once you’re licensed, Yoga Support enables the solution in your production environment. Enablement includes the Statement document type, the Statements Automation queue, and the Statements Automation view.

Back to Top

---

How Statements Get Into Yoga 

Intent

Get vendor statements into Yoga through the same channels you already use for invoices, so no one has to hand-key statement data.

Ways to use it

Statements arrive through three paths:

Upload / capture page. Upload a statement PDF directly from a capture page. During the Test Tenant free trial this is the only way to ingest a Statement via the Statement Matching capture page, which also shows your usage against the monthly limit.

Email. Point your vendors (or forward statements) to your Yoga email connector. Yoga classifies the inbound document, recognizes it as a statement rather than an invoice, and routes it to the Statements Automation queue. The originating email details are kept on the record so you can always see who sent it and when.

Excel or CSV (opt-in). If your vendors send statements as spreadsheets, Yoga can bulk-capture them through a dedicated Data Capture page — the same pattern as invoice spreadsheet upload. Yoga creates the statement records, maps header and activity lines, and generates a viewable statement image so your team still works the data visually. This requires the Statement Matching solution first, and is configured per organization. Email YogaSupport@RPIC.com to request it.

Technical overview

• Classification: inbound documents pass through Content Understanding classification, which distinguishes statements from invoices and routes accordingly. Capture pages also allow manual classification (auto, invoice, statement, other).
• Extraction: the statement intake process reads the vendor header (name, number, address, Federal ID), statement metadata (date, period, balances, account number and name, currency, contact details), and every activity line.
• Vendor identification: Yoga resolves the vendor from the statement content and the sending email address against your vendor master. If it cannot identify the vendor with confidence, the statement lands in Needs Vendor for a person to assign — matching cannot run until the vendor is known.
• Multi-page statements stay intact as a single record after ingestion; long statements are no longer split into partial records.
• Auto-matching runs immediately at intake, before anyone opens the record.

Back to Top

The Statements Automation View 

Intent

Give the team a single prioritized worklist of every statement in flight, plus an at-a-glance read on total reconciliation exposure.

Ways to use it

Start the day in the summary cards to see where the work is: how many statements need review, how many are waiting on a vendor reply, how many are still missing a vendor, and how many are done. Then work the list beneath it, oldest first, filtering to one vendor when you’re doing a scheduled account review.

Technical overview

Summary cards  sit in a single strip of eight across the top of the view. The first five are live counts of statements, in left-to-right order: Needs Review, Reconciled, Needs Vendor, Pending Vendor, and Disputed. The first four are simply how many statements currently hold each of the statuses described in the Statement Statuses section; Disputed counts statements carrying the separate disputed flag rather than a fifth status. 

The remaining three cards are reconciliation metrics rolled up across the statements in the view. Matched Lines and Matched Amount are each shown as a fraction — the matched figure over the total — so the two totals are denominators inside those cards rather than cards of their own:

Card	What it shows
Matched Lines	Lines matched to an AP document, over total lines across the statements in view (for example, 7 / 9)
Matched Amount	Value of matched lines, over total statement value (for example, $61,430 / $74,267)
Accrual	Total value of lines currently accrued

Ignored lines are excluded from every count and total, so dismissing a line that doesn’t apply genuinely reduces your exposure numbers rather than just hiding a row.

List columns: Status · Disputed · Vendor ID · Vendor Name · Time since creation · Account Name · Notes. Every column filters, and Status and Disputed offer preset filter options so you can jump straight to a work state.

Back to Top

Statement Statuses 

Intent

Tell you, without opening the statement, whether the ball is in your court or the vendor’s.

Technical overview
Every statement carries exactly one status, calculated automatically from its lines. Yoga applies the first rule that fits — there is no fall-through:


Two useful consequences of the way this is calculated:

• Credit lines never create work. A line with a negative amount is treated as a credit and is skipped by the status rules. A statement made up entirely of credits reconciles on its own.
• A statement with a vendor and no activity lines is Reconciled, not stuck in review.

Disputed is a separate flag, not a status. Marking a statement disputed does not change its Needs Review / Pending Vendor / Reconciled status — it’s an annotation you can filter on in the view.

Back to Top

Working a Statement 

Intent

Put everything needed to reconcile a statement — the vendor, the statement image, every line, and every AP fact about that line — on one screen.

Technical overview

Header sections (read-only, populated at intake):

Section	Fields
Vendor Information	Vendor Name · Vendor Number · Vendor Address · Federal ID
Statement Details	Statement Date · Statement Period · Statement Balance · Closing Balance · Account Number · Account Name · Currency · Contact Phone · Contact Email · Description
Email Connector Details	Source · To Email · From Email · Subject Line · Date Emailed · Importance · Email Job Run ID

The line grid (“Statement Invoices”) is where the work happens. Its columns come from three places:

Read from the statement: Invoice # · Invoice Date · Due Date · PO Number · Statement Amount

Set by you as you work: Matched · Accrual Status · Vendor Contacted · Ignored

Brought over from the matched AP document (read-only): AP Queue · AP Amount · Payment Status · Check Number · Payment Date · Payment Amount · PO Code · Received Status · Received Date · Receipt detail · Last Comment · Tax Amount · Subtotal · Company Number · Company Name

Matched lines show a green check that links straight to the source AP document, so you can open the invoice Yoga matched and confirm it yourself in one click.

Grid controls. You can show, hide, resize, and reorder columns, and your layout is saved per user — so a processor who only cares about payment status can build that view once and keep it. A filter indicator tells you when filters are narrowing the grid, with one-click reset. Download to CSV exports the full statement — all rows and all columns, including ones you’ve hidden.

Back to Top

Automatic Matching - in development: coming in V2

Intent

Resolve every line Yoga can prove, so people only handle genuine exceptions.

Ways to use it

You generally don’t run matching — it runs for you, twice:

• At intake, as soon as the vendor is identified. This is why a statement is often already largely reconciled the first time anyone opens it.
• On a recurring schedule afterwards, so a line that couldn’t match on Tuesday (because the invoice hadn’t been keyed yet) matches on its own by Thursday. The same job refreshes payment and receipt details on already-matched lines, so a statement you accrued last week reflects this week’s payment activity without being reopened.

Because matching re-runs, the right response to an unmatched line for an invoice you know is in flight is usually to accrue it and let the next sweep pick it up.

Technical overview

Matching requires a vendor on the statement, and only considers lines that aren’t already matched, aren’t credits, and have both an invoice reference and a readable amount.

Yoga searches your open and completed AP documents — including EDI invoices and invoices already in AP Paid — across every invoice document type configured for your organization. Packing slips are excluded.

A candidate must satisfy all of these to be matched:

Criterion	Rule
Vendor	Exact match on vendor number
Invoice number	Exact match, not case sensitive
Amount	Matches to within half a cent
PO number	If both sides have a PO, they must agree. If neither has one, that’s fine. If the statement line has a PO and the AP document doesn’t (or vice versa), the match is rejected.

When more than one AP document satisfies every criterion, Yoga takes the most recently updated one. On a successful match, the line is linked to that document and the AP queue and AP amount are stamped onto the row, followed by the payment and receipt detail columns.

If a previously matched line can no longer be synced — the AP document was deleted, is mid-routing, or was changed by someone else at the same moment — Yoga surfaces that as a match failure on the row and the statement returns to Needs Review rather than silently keeping stale data.

Back to Top

Line Actions 

Intent

Give a reviewer a small, unambiguous set of moves for any line, and let the statement status follow automatically.

Technical overview

Every line carries its own action control at the end of the row. Accrue is the primary button, and the rest of the actions sit behind the dropdown beside it, in this order: Research, Match, Email, Ignore, and Remove. Two actions are contextual and replace the primary button rather than sitting in the dropdown — a line that is already matched offers Unmatch, and a line that is already ignored offers Unignore — so the action that undoes a line’s current state is always the one in front of you.

Action	What it does	Effect on status
Match	Links the line to an AP document, stamps AP queue and amount, and pulls in payment and receipt detail. Yoga also records on the AP document that it appears on this statement.	Removes the line from outstanding work
Unmatch	Breaks the link, clears the derived payment and receipt columns, and removes the reference from the AP document	Returns the line to outstanding work
Accrue	Books the line as an accrual, for statement activity you believe is real but can’t yet find in AP	On its own, still Needs Review — until the vendor is contacted
Research	Opens the research panel for this line and searches your AP data for candidate documents. See Research Tool.	None — it is a lookup, and nothing changes until you act on a result
Email	Emails the vendor about this line on its own, rather than about the whole statement. See Emailing the Vendor.	None on its own — the Vendor Contacted flag is what moves the status
Ignore	Dismisses the line from reconciliation. The line stays on the statement, flagged as ignored.	Excluded from all counts, totals, and work states
Unignore	Returns an ignored line to reconciliation	The line counts again, and becomes work if it is unmatched
Remove	Deletes the line from the statement	The line no longer exists, so it cannot contribute to any count, total, or status
Vendor Contacted	A flag on the line — the Vendor Contacted column in the grid — recording that you’ve asked the vendor about this line	An accrued and contacted line moves the statement to Pending Vendor

Ignore and Remove are not the same thing, and the difference has consequences. Ignore flags the line as ignored but leaves it on the statement: you can still see it in the grid, it still comes out in the CSV export, and it still appears on the line-level Statement Report marked as ignored. What it loses is any influence — it drops out of the matched-lines, matched-amount, and accrual figures, and it can never put the statement into Needs Review.

Remove deletes the line from the statement’s line data outright. Every total is recalculated without it, it is gone from the grid and from the CSV export, and the recurring match sweep will never bring it back, because matching only ever works on lines that are on the statement. If the line you remove was matched to an AP document, Yoga also removes this statement’s reference from that document. What survives is the statement’s change history, which records the removal along with the values the line held at the time — so there is still an audit record that the line was once on the statement, even though the statement no longer carries it. Remove is shown in red in the menu for that reason.

Use Ignore for a line that doesn’t apply, and Remove only for a line that should never have been on the statement in the first place — a row extraction duplicated, or a heading or subtotal it read as activity. Ignore leaves visible evidence on the statement that someone looked at the line and dismissed it; Remove does not.

The intended path for an unmatched line is accrue, then contact the vendor. A line that’s been accrued but not contacted still shows as work, as does a line that’s been contacted but not accrued. Only when both are true does the statement move to Pending Vendor. Note that sending a vendor email is recorded on the statement as a whole — Yoga stores that a vendor email went out and when — while Vendor Contacted is per line, so it is the line flag, not the send, that the status calculation reads.

Accruals must be reversed once a line matches. If a line you accrued later matches to a real AP document, the statement goes back to Needs Review specifically so someone reverses the accrual — it won’t quietly reconcile with a duplicate accrual sitting on the books.

Back to Top

 Research Tool 

Intent

Answer “is this actually in our AP anywhere?” for a stubborn line, without leaving the statement and without running four separate searches.

Ways to use it

Open the research panel on any line you can’t resolve. Yoga runs four searches at once and returns what it finds in each. Use it when the vendor’s invoice number doesn’t quite match yours (a prefix, a suffix, a leading zero), when you suspect the invoice was keyed under a different vendor record, or when you want to prove a line was already paid before you tell the vendor so.

Technical overview

The research panel searches on the line’s invoice reference, amount, PO number, and invoice date, scoped to the statement’s vendor. At least an invoice reference or an amount is required. Four searches run in parallel:

Search	What it looks for
Invoice number	Exact matches, plus partial matches in either direction — the statement reference contained in your invoice number, or your invoice number contained in the statement reference — where the two differ in length by no more than two characters. This is what catches prefixes, suffixes, and check-digit differences.
Amount	AP documents for the same amount, optionally narrowed to within 30 days either side of the statement line’s invoice date, most recent first
PO number	AP documents on the same PO
Payment	Payment activity for the amount, matched to within a penny, optionally narrowed to the same 30-day window

Each search returns up to 10 results, enriched with payment detail, tax and subtotal, company, PO, and the queue the document currently sits in — so you can judge a candidate from the results list rather than opening each one.

Other-vendor results. Yoga also runs a second bucket looking outside the statement’s vendor, using fuzzy vendor-name similarity. This is how you find an invoice keyed under a duplicate or differently-named vendor record — a common reason a legitimate line looks missing.

Results are candidates, not decisions. You confirm the match.

Back to Top

 Payment & Receipt Details 

Intent

Answer the vendor’s actual question — “was it paid, and when?” — on the statement itself.

Technical overview

Once a line is matched, Yoga carries the AP facts onto the row: Payment Status, Check Number, Payment Date, Payment Amount, plus tax, subtotal, and company. These are refreshed by the recurring sweep, so they stay current without reopening the statement.

Receipt detail is available for Infor FSM organizations. For matched lines with a PO, Yoga performs a live receipt lookup against FSM and shows a rolled-up Received Status — Received, Partially Received, or Not Received — with the received date and the underlying receipt detail. The lookup runs immediately when you match a line, so you see receiving status without waiting for a save. Where a PO can’t be found or resolves ambiguously, Yoga displays nothing rather than guessing.

Organizations on other ERPs will see the payment columns populate but not the receipt columns.

Back to Top

 Emailing the Vendor 

Intent

Close the loop on unresolved lines in one step, with a status table the vendor can actually act on — instead of a thread of “can you resend invoice 4471?”

Ways to use it

When lines can’t be resolved internally, email the vendor from the statement. Yoga builds the message for you: your vendor’s header details, a formatted table of the lines in question with the status of each, and totals. Review it in the preview, adjust the wording, add recipients, and send. Use it for a whole statement, or for a single line when only one item is in question — in that case the totals block is omitted so the email stays focused.

After sending, mark the lines as Vendor Contacted so the statement moves to Pending Vendor and drops off today’s worklist.

Technical overview

The status table includes: Invoice # · Invoice Date · Due Date · PO Number · Amount · Status, where status is shown as Received, Not received, or Credit. Below it, a totals strip shows Statement Total, Received, and Not received, with Not received highlighted when non-zero.

Attachments. Every email automatically includes an Excel workbook of the same table, named for the vendor and statement date, with amounts as real numbers so the vendor can sort and total them. You can optionally attach a PDF of the statement itself.

Sending. The email goes out under your organization’s branding with your name and email as the reply-to, so the vendor’s reply comes back to you directly. Yoga records on the statement that a vendor email was sent and when.

Limits. Up to 5 recipients, a 200-character subject, a 2,000-character message body, and up to 200 lines in the table.

Vendor replies come back to your mailbox, not into Yoga. Yoga sends the outbound email; it does not currently ingest the reply and update the statement automatically. You resolve the lines on the statement when the vendor answers.

Back to Top

 Accruals & Export 

Intent

Turn the accruals you booked while reconciling into something your ERP can consume at close.

Ways to use it

Work statements as normal through the month, accruing lines the vendor claims but you can’t find. At close, export accrued items to Excel or CSV for upload into your ERP. The Accrual Amount total on the summary cards gives you the running exposure figure before you export.

Note that the recurring match sweep works in your favor here: lines you accrued early in the period often match on their own before close as the invoices are keyed, which drops them out of the accrual and flags the statement for reversal.

Back to Top

 Disputes & Notes 

Disputed is a flag you set on a statement to mark it as under dispute with the vendor. It’s deliberately independent of the workflow status — a disputed statement can still be Needs Review or Pending Vendor — and it’s filterable in the view and counted on the summary cards, so disputes stay visible without distorting your reconciliation queue.

Notes use Yoga’s standard document notes, visible as a column in the statement list. The most recent comment from the matched AP document is also surfaced as a read-only Last Comment column on the line, so a processor working the statement can see what the AP team already said about that invoice.

Back to Top

 Permissions 

Access to statements uses the same view and document permission model as the rest of Yoga — if a user can see the Statements Automation view, they can work the statements in it. Ask Yoga Support to adjust who has access.

Two specific rules apply:

• The Statements Automation view is hidden when the solution is first enabled and must be turned on for your organization.
• Sending vendor emails from a statement requires an internal organizational account. External guest accounts can work statements but cannot send or preview vendor emails.

During the free trial, capture is limited to Yoga Super Users.

To change statement permissions for your organization, email YogaSupport@RPIC.com.

Back to Top

 Reporting 

Day-to-day reporting is built into the Statements Automation view — the summary cards give you live counts and dollar totals by status, and every statement’s line grid exports to CSV in full.

A detailed line-level Statement Report also exists, covering statement date, vendor, statement number and status, and every line with its invoice reference, dates, PO, amount, accrual status, matched flag, vendor-contacted flag, and last change. This report is not currently exposed in the standard client reporting experience — email YogaSupport@RPIC.com if you’d like it run or made available for your organization.

 

Back to Top

FAQ

Is Statement Matching included in my current Yoga license?

No. It’s a separate solution and an addition to your platform fee.  Contact your Client Success Manager or YogaSupport@RPIC.com for pricing.

Can we try it before we buy it?

Yes. You can process up to 5 statements per calendar month in your TEST environment, with your own statements and your own AP data. No rollout request is needed — Yoga Super Users can start from the Statement Matching capture page. The limit resets each calendar month.

When you say “matching,” do you mean matching to the statement or matching within our ERP?

Matching to the statement. Yoga matches each statement line against your AP documents in Yoga. It does not perform invoice-to-PO or receipt matching in your ERP, and it isn’t a three-way match. Receipt and payment details are displayed on matched lines for context.

Why is a statement stuck in Needs Vendor?

Yoga couldn’t identify the vendor from the statement or the sending email address with enough confidence. Assign the vendor on the record and matching will run.

Why didn’t a line match when I can clearly see the invoice in AP?

The most common causes are an invoice number that isn’t an exact match (a vendor prefix or suffix), an amount that differs by more than half a cent, or a PO number on one side but not the other — Yoga will not match a statement line that carries a PO to an AP document that doesn’t. Use the research tool; its partial invoice-number search and other-vendor search are built for exactly these cases.

Why did a reconciled statement go back to Needs Review?

Almost always because a line you had accrued has since matched to a real AP document. Yoga reopens the statement so the accrual gets reversed rather than leaving a duplicate accrual on the books. It can also happen if a matched AP document was deleted or changed and the link could no longer be synced.

Do I have to re-run matching?

No. Matching runs at intake and then on a recurring schedule, so lines for invoices that hadn’t been keyed yet match on their own. The same sweep refreshes payment and receipt details on lines that are already matched.

Will paid invoices match?

Yes. Matching includes invoices already in AP Paid, as well as EDI invoices.

What happens to credits on a statement?

Credit lines (negative amounts) are recognized as credits and never create work. A statement consisting entirely of credits reconciles on its own.

What’s the difference between Ignore and Unmatch?

Ignore dismisses a line from reconciliation entirely — it drops out of every count and total. Unmatch only breaks the link to an AP document and puts the line back into outstanding work.

Do we see receipt information?

Received status, received date, and receipt detail are available for Infor FSM organizations on matched lines with a PO. Organizations on other ERPs see payment columns but not receipt columns.

What does the vendor actually receive when I email from a statement?

A branded email with your message, a formatted table of the lines in question (invoice number, dates, PO, amount, and Received / Not received / Credit status), totals, and an Excel copy of the same table attached. You can also attach the statement PDF. Replies come back to you.

Does Yoga process the vendor’s reply?

Not today. The reply comes to your mailbox and you resolve the lines on the statement. Inbound reply handling is on the roadmap.

Our vendors send statements as spreadsheets, not PDFs. Can Yoga handle that?

Yes, as an opt-in. Yoga can bulk-capture statements from Excel or CSV and generate a viewable statement image so your team still works the data visually. It requires the Statement Matching solution first and is configured per organization. Email YogaSupport@RPIC.com.

Can I change which columns I see on the statement grid?

Yes. Show, hide, resize, and reorder columns; your layout is saved to your user. CSV download always exports the full statement, including columns you’ve hidden.

Questions? Email YogaSupport@rpic.com and we’ll connect you with the right person on our team.

 

Back to Top