Payment, refund, and cancellation records converge into a reconciliation check between PayPal activity and an Acumatica ledger

PayPal and Acumatica payment reconciliation is the process of matching each customer payment request, collection, refund, and cancellation to the corresponding PayPal record and Acumatica Accounts Receivable (AR) document. A reliable review uses stable invoice, transaction, and refund identifiers; compares amounts in the same currency and period; and separates customer-facing invoice status from cash movement and ERP posting. The result should explain every open balance and every difference, rather than treating a synchronized status as proof that the books are complete.

This guide is for finance teams using or evaluating the Biz-Tech Services PayPal Integration for Acumatica. It concentrates on the daily and month-end control after an invoice has been sent. Biz-Tech's existing connector walkthrough explains the screen-by-screen data flow, while its payment and order-status lesson explores operational effects. Here the question is narrower: how can a reviewer demonstrate that the PayPal lifecycle, AR payment, fees, refunds, and eventual bank movement agree?

Start with three separate records

A customer may see a PayPal invoice as paid while the ERP payment is still on hold. A PayPal refund may exist before a credit memo is posted. A PayPal balance may be lower than gross receipts because fees or transfers changed the account. These are not necessarily errors; they are different records with different purposes and timing.

The first record is the PayPal invoice and its payment or refund history. It answers what the payer was asked to pay, what PayPal has recorded, and the current invoice state. The second is the Acumatica AR payment and any related credit or void document. It answers what has been applied and released in the ERP. The third is PayPal account activity and bank settlement. It answers where the cash and fees went. PayPal describes its Balance Report as a source for reconciling sales, refunds, disputes, fees, withdrawals, and end-of-day balances. Availability and delivery of a particular report depend on the merchant account, so confirm the report used by your organization.

Do not collapse these records into one “paid” flag. A status can confirm an event while the amount, currency, date, or accounting treatment still needs review. Use one reconciliation row per meaningful event or document, then roll up to the customer invoice and reporting period.

Back to TOC

Define what is being reconciled

Write down the scope before exporting data. Decide whether the review covers PayPal invoices initiated in Acumatica only, all PayPal merchant transactions, or both. If other commerce channels also use the merchant account, a PayPal balance report will contain activity that has no Biz-Tech connector payment request. That activity needs its own owner and mapping; it should not be forced onto an unrelated Acumatica invoice.

Set a cutoff in a named time zone. Record the PayPal event time, the time of the connector's last status check, the ERP document date and release time, and the balance-report period. A payment received minutes before midnight can appear in one day's provider activity and the next day's ERP review. Classify that as a timing item until the expected posting window expires; do not silently move the transaction between periods.

Define the balances under review: open AR, released AR payments, refund or credit documents, PayPal merchant balance, fees, and bank transfers. A matched invoice-to-payment control does not by itself reconcile fees or bank deposits. Finance should sign off each layer separately and then tie the layers together.

Back to TOC

Map identifiers before comparing amounts

The PayPal invoice ID is the strongest bridge from a PayPal invoice to the ERP request. PayPal's invoice object documentation identifies the PayPal-generated invoice ID and distinguishes it from an invoice number and the invoice's current status. Biz-Tech's data-flow guide says its connector writes the PayPal Invoice ID, URL, and invoice number to the Acumatica payment record.

For every reconciliation row, retain the Acumatica payment reference, PayPal invoice ID, invoice number, customer, currency, original amount, current invoice status, last status-check time, and related transaction or refund ID. For a bank transfer, add the payout or transfer reference and bank posting reference. If an ID is absent, create an exception rather than matching solely on customer name and amount; two customers can pay the same amount on the same day.

Do not assume a one-to-one relationship between invoice and collection event. PayPal allows partial payments, and an invoice can carry payment and refund history. Multiple events may be needed to explain one invoice balance. Maintain the event sequence instead of overwriting the original payment row with its latest status.

Back to TOC

Read PayPal invoice states precisely

PayPal's invoice lifecycle distinguishes SENT, PARTIALLY_PAID, PAID, PARTIALLY_REFUNDED, REFUNDED, and CANCELLED. A sent invoice remains payable. A partially paid invoice has a reduced but still open balance. A fully paid invoice reflects full collection through the hosted payment flow. A partial or full refund changes the economic position after collection. A cancelled invoice is a withdrawn request, not a refund of cash already collected.

PayPal also documents MARKED_AS_PAID and MARKED_AS_REFUNDED states for activity recorded manually outside the hosted payment or refund flow. Do not treat a manually marked paid invoice as proof of a PayPal cash receipt. Identify the external payment method and supporting bank evidence. The distinction matters when the same invoice is present in both PayPal and ERP but the actual money arrived by check or bank transfer.

An invoice status is a current summary, not a full audit trail. Review the underlying payment and refund events when amounts do not agree. PayPal's Invoicing API reference describes retrieval of an invoice with payment and refund history. The exact fields and available actions depend on API version and account configuration; use the live object and your connector's documented mapping as the authority.

Back to TOC

Understand the documented Biz-Tech connector flow

The Biz-Tech PayPal Integration page describes invoices sent from Acumatica, on-demand status synchronization, bulk processing, cancellations, and refunds. Its published data-flow guide says an AR payment is held after a request is sent, then a status check updates the record. Under the documented behavior, a PAID state releases the payment; PARTIALLY_PAID updates the collected amount but leaves the payment on hold; REFUNDED uses the void workflow; and CANCELLED removes the held payment record.

This article treats those statements as the currently published Biz-Tech workflow, not a guarantee that every installed connector version behaves identically. Before relying on automated release or deletion, compare the customer's deployed package, customization, payment method setup, Acumatica build, and operational runbook with those descriptions. Record who can trigger status checks and who reviews exceptions.

The same guide identifies the PayPal status-check screen as a daily worklist. A reviewer should capture the last check time and result. A payment that has not yet been checked is different from a failed synchronization or a genuinely unpaid invoice. Do not let an old status linger without an age threshold or owner.

Back to TOC

Reconcile a fully paid invoice

Start with the PayPal invoice ID on the AR payment. Confirm that the invoice is the one sent to the customer and that its currency, recipient, and amount match the ERP request. Then inspect PayPal's payment history for the collection event and its unique transaction reference. Verify the amount and event time. Finally, confirm that the Acumatica AR payment has been updated and released according to the deployed connector workflow, and that the payment is applied to the intended invoice.

The reconciliation is complete at the customer-balance layer only when the AR invoice balance, payment application, and PayPal paid amount agree. A released payment applied to the wrong invoice is still an exception. A PayPal PAID status on an invoice with the wrong currency or an old customer payment method also needs investigation.

Keep the provider transaction reference in the review record. It helps distinguish a later reversal or refund from a duplicate status message. Then reconcile the gross collection to PayPal account activity and any fees separately. A payment can be correct in AR while the PayPal-to-bank bridge remains open.

Back to TOC

Handle partial collections without closing the invoice early

PayPal's PARTIALLY_PAID state means the customer has paid only part of the requested amount and a balance remains open. The Biz-Tech connector guide says a partial collection updates the paid amount and leaves its AR payment on hold. That is a control point: the record should not be treated as a fully settled invoice merely because some money has arrived.

For each partial payment, compare the new PayPal event to the prior cumulative paid amount and remaining balance. Retain both the event amount and the running total. If a later payment completes the invoice, verify the final state and the AR release only after the full amount is supported. If the customer pays in several installments, the event history should explain the total without counting a status refresh as another receipt.

Finance should decide how partial receipts are represented in AR under the deployed customization and accounting policy. Do not assume that changing the held payment amount is equivalent to posting a new cash receipt. The reviewer should check the actual Acumatica document status, application, and GL impact before closing the exception.

Back to TOC

Distinguish a cancellation from a refund

A cancellation withdraws a sent request that has not been paid. A refund returns value after collection. PayPal's Invoicing API retains cancelled sent invoices for record keeping, whereas deleting a draft or scheduled invoice is a different action. The published Biz-Tech connector guide says its Cancel PayPal Invoice action applies to a sent, held request and removes the related AR payment after PayPal cancellation. Confirm the exact preconditions in the installed version before using the action.

The cancellation control should compare the PayPal invoice status, the ERP held payment, and the customer notification. If the ERP payment is gone, preserve its former reference and PayPal invoice ID in an audit or exception record. Otherwise a reviewer may later see a cancelled PayPal invoice with no ERP record and be unable to explain it.

Do not “cancel” a paid request to undo cash. If money was collected, follow the refund or void workflow supported by the provider, the connector, and company policy. That distinction prevents a customer credit from being recorded without the corresponding payment reversal.

Back to TOC

Reconcile full refunds

The Biz-Tech connector walkthrough describes a full refund initiated from a released AR payment through Acumatica's Void Check or Refund action, with a PayPal refund request and refund ID recorded back on the payment. PayPal's refund documentation explains that a provider refund is tied to the original capture and that its resulting event should be tracked. For an invoicing payment, validate the actual PayPal invoice and transaction references used by your connector.

To close a full refund, match the original collection, refund amount, refund ID, PayPal invoice state, ERP void or refund document, customer balance, and provider balance activity. The refund can settle after the status first changes, depending on the payment method and provider workflow. Keep a pending item until the amount appears in the provider activity or a supported explanation exists.

A full refund should not be counted both as a void of revenue and as an unrelated expense. The accounting treatment depends on the original sale, tax, credit memo, and ERP configuration. Finance should verify the resulting AR and GL documents rather than relying on a connector status label alone.

Back to TOC

Control partial refunds as exceptions

Partial refunds are the most important boundary to document. The published Biz-Tech PayPal data-flow article says that a partial refund initiated in the PayPal portal is detected on the next status check and its refund ID and PARTIALLY_REFUNDED state are recorded, but the connector does not automatically create a partial void of the AR payment. Its documented remedy is a manually prepared credit memo for the refunded amount, subject to the organization's approval and accounting process.

That makes status synchronization and accounting completion separate steps. An exception should remain open until the refund is visible in PayPal, the ERP credit or adjustment is approved and posted, the customer balance is correct, and any tax or revenue treatment has been reviewed. Do not mark the exception closed merely because the PayPal status updated.

Record why the partial refund occurred: short shipment, price adjustment, service issue, tax correction, or another supported reason. The reason determines whether a credit memo, invoice adjustment, return, or other document is appropriate. The exact accounting and tax treatment is jurisdiction and transaction specific; the connector status does not decide it.

Back to TOC

Separate customer balances from fees and PayPal cash

Customer AR and provider cash are related but not identical. A customer may pay the gross invoice amount while PayPal deducts processing fees before the merchant balance or bank transfer changes. PayPal's reconciliation documentation distinguishes transaction-level sales, refunds, and fees and explains that fee settlement models can differ. The Biz-Tech connector's published feature description should not be read as a promise that every fee is automatically posted to the right Acumatica account.

Map gross customer collection to AR first. Map fees to the approved expense and PayPal clearing accounts separately. Then reconcile the change in PayPal merchant balance. If a refund also occurs, verify whether any associated fee adjustment appears in the provider report; do not apply a universal fee-reversal assumption.

The same separation applies to disputes, reserves, foreign exchange, and withdrawals. Where the merchant account contains activity outside this connector, create distinct transaction types and owners. A daily summary total is useful only when its components can be traced to source events.

Back to TOC

Match PayPal balance activity to the bank

An invoice-to-AR match establishes that a customer payment was recorded correctly. It does not establish that the money reached the bank. Use PayPal's available balance or reconciliation report to bridge beginning balance, collections, refunds, fees, disputes, withdrawals, and ending balance. Then compare withdrawals or transfers to bank statement lines by reference, amount, currency, and settlement date.

Keep timing items explicit. A transfer initiated late in one period may reach the bank later. An unmatched bank line could also represent a consolidated payout that combines many payments. Reconcile at the payout level and retain the underlying transaction detail; do not force a one-bank-line-to-one-customer-invoice match.

If the report uses a currency different from the AR invoice or bank account, document the rate and conversion source used by the company's accounting policy. PayPal notes that some fee settlement models and currencies require separate analysis. A difference caused by currency conversion should be measured and approved, not hidden inside a generic “fees” line.

Back to TOC

Build a daily exception queue

An actionable queue needs the invoice ID, ERP payment reference, customer, currency, gross amount, provider status, ERP status, last check time, event date, amount difference, age, category, owner, and next action. Add transaction and refund IDs where applicable. Keep a link or reference to the source report rather than copying sensitive credentials into the worklist.

Use clear categories: not yet checked; provider paid but ERP held; ERP released but provider not paid; partial payment; cancellation pending; full refund pending; partial refund awaiting ERP credit; fee mapping; bank transfer timing; duplicate or missing identifier; and unresolved. Assign thresholds by business risk and payment volume. A same-day status delay may be routine, but an aged unreleased payment or unmatched refund is not.

Review new and aged exceptions separately. A short queue with named owners is more useful than a dashboard with a large “out of balance” total. Close each line with supporting event references, the ERP correction, approval where required, and a reason that can inform prevention.

Back to TOC

Use a reproducible investigation sequence

First confirm that the compared records belong to the same merchant account, invoice ID, customer, and currency. Second compare the event history, not just the latest invoice status. Third read the connector's last status-check result and the Acumatica document state. Fourth inspect PayPal balance activity and any bank transfer. Finally decide whether the difference is timing, mapping, missing event, rejected ERP action, or accounting treatment.

Do not repeat a refund or cancellation action just because the UI response was slow. PayPal's REST request guidance describes the PayPal-Request-Id header for idempotent supported POST calls. Whether the Biz-Tech connector uses that mechanism in a particular version must be verified in the deployed integration. When an action's outcome is uncertain, inspect the provider resource and ERP document before retrying.

Keep correction and cause separate. “Re-ran the status check” is an action; “the prior check failed after the PayPal event” is a cause. That distinction prevents recurring differences from being dismissed as isolated manual fixes.

Back to TOC

Test failure and retry paths

A test plan should include a fully paid invoice, two partial payments, an unpaid cancellation, a full refund, a PayPal-portal partial refund, a provider event arriving after the ERP cutoff, and a failed or repeated status check. For each scenario, record the expected PayPal state, the expected Acumatica document, the report activity, and the exception queue outcome.

Do not assume all integrations use webhooks. PayPal supports invoicing webhooks for invoice events, but Biz-Tech's public connector documentation describes status checks on demand and in bulk. If a deployment also uses webhooks, test event verification, duplicate delivery, and recovery separately. A webhook notification should trigger investigation or processing; it is not itself proof that the ERP document posted.

Use sandbox and representative ERP test data where possible. Include mixed currencies, repeated customer names, two invoices with the same amount, a refund after period close, and a transfer that crosses a bank statement date. Retain test evidence and sign-off before changing the production workflow.

Back to TOC

Assign review ownership and close evidence

Customer service or sales operations may own the reason for cancellation or refund. AR owns customer balances and applications. Treasury or cash management owns PayPal clearing and bank transfers. Integration support owns status-check failures, identifier mapping, and connector recovery. Finance leadership owns thresholds, policy, and final sign-off. One person can hold multiple roles in a small team, but the queue still needs named responsibility.

For each closed exception, retain the PayPal invoice and event IDs, the ERP payment and credit references, gross and refund amounts, provider report row, bank transfer reference where relevant, approval, correction, and root cause. Avoid storing PayPal secrets or private customer payment details in the review file. Access to the evidence should follow the organization's controls.

At month end, review aged items, manual credits, unusual fee differences, and transactions that crossed the cutoff. Reconcile the PayPal clearing account and bank transfers to the approved ledger. A clean invoice status list without a clearing-account reconciliation is incomplete.

Back to TOC

A worked reconciliation example

Consider a hypothetical USD 1,000 PayPal invoice created from Acumatica. The customer pays USD 1,000, so the PayPal invoice reaches PAID and the documented connector workflow releases the AR payment. The customer later receives a USD 100 partial refund from the PayPal portal. A status check records PARTIALLY_REFUNDED and the refund ID, but the published Biz-Tech workflow requires a separately reviewed ERP credit for the partial refund. Assume, for illustration only, that PayPal charges USD 29 in fees and that no other transactions affect this merchant balance.

At the customer layer, the original USD 1,000 collection and the approved USD 100 credit leave USD 900 of net customer consideration. At the provider layer, USD 1,000 collected minus USD 100 refunded minus USD 29 fees produces USD 871 of net PayPal balance activity before any bank transfer. The USD 29 difference between customer consideration and provider cash is a fee, not an unpaid customer balance. If PayPal transfers USD 871 to the bank, the clearing account should explain that transfer with the payment, refund, and fee lines.

Those figures are illustrative, not a claim about PayPal pricing, fee refunds, timing, or the connector's automatic GL postings. The actual report, contractual fees, refund terms, accounting policy, tax treatment, and deployed connector behavior determine the real entries.

Back to TOC

Implementation checklist

Begin with a one-page data map: which Acumatica document creates the PayPal request, where the PayPal invoice ID is stored, which status check updates it, and which document records a full or partial refund. Confirm the installed Biz-Tech connector version and its behavior with the PayPal Integration documentation and a representative transaction.

Next build a daily extract with invoice IDs, ERP references, status timestamps, amounts, currencies, transaction IDs, refund IDs, and PayPal balance-report references. Define the shared cutoff and the approved fees, clearing, and bank-account mappings. Run the reconciliation in parallel with the current finance process until the exception categories and ownership are stable.

Finally test the failure paths, approve the close checklist, and review the results after any Acumatica upgrade, connector change, or PayPal configuration change. Biz-Tech Services can help assess the connector and payment flow against the actual AR and treasury process. The most useful starting evidence is a small sample of paid, partially paid, cancelled, fully refunded, and partially refunded invoices with their matching ERP and provider records.

Back to TOC

Frequently Asked Questions

Does a PayPal PAID status prove that Acumatica AR is correct?

No. Confirm the Acumatica payment was released and applied to the intended invoice, and compare the amount and currency. Then reconcile provider fees and bank movement separately.

What should be the primary matching key?

Use the PayPal invoice ID together with the Acumatica payment reference. Add transaction and refund IDs for individual events. Customer name and amount alone are not reliable unique keys.

Is a cancelled invoice the same as a refunded payment?

No. Cancellation withdraws an unpaid request. A refund returns value after collection and needs a matching provider and ERP accounting record.

What happens to a partial payment in the published Biz-Tech connector workflow?

The published connector guide says the collected amount is updated while the AR payment remains on hold. Verify the behavior in the deployed version and inspect the actual document before treating the invoice as settled.

Does a PayPal-portal partial refund automatically create an Acumatica credit?

The published Biz-Tech guide says no partial void is created automatically for that path; it calls for a manually prepared credit memo. The credit requires the organization's normal approval, tax, and accounting review.

Should a status check be rerun when the result is uncertain?

First inspect the PayPal invoice and ERP document to determine whether the previous action succeeded. Avoid repeating a financial action blindly. A status refresh and a refund request are different operations.

Why is the PayPal deposit lower than the customer payment?

Provider fees, refunds, disputes, reserves, currency conversion, and timing can change the merchant balance or payout. Use the provider's transaction-level reconciliation report to identify the actual components.

How should multiple payments against one invoice be reviewed?

Keep each event and its transaction reference, reconcile their cumulative amount to the invoice balance, and confirm the ERP document reflects the correct final state.

What belongs in the month-end sign-off?

Include open AR exceptions, partial refunds awaiting credits, PayPal clearing balance, fees, disputes, transfers in transit, bank matches, corrections, and reviewer approval.

Do PayPal webhooks replace reconciliation?

No. Webhooks can notify an integration that an invoice event occurred, but the ERP document, provider activity, and bank movement still need to be checked. Confirm whether the deployed connector uses webhooks at all.

Back to TOC

Sources

Back to TOC

Privacy Preference Center