Reports and Dashboards
Payment and AR Object Fields
Field guide for Payment Orders, Payment Transactions, saved methods, receipts, invoices, and AR reporting
Payment and AR reports should separate intent, transaction evidence, receipt evidence, invoice state, and saved payment method state. These objects answer different questions.
Payment Object Map
Payment Order
Payment Orders are collection intents. Use them when the report question is about what should be collected, payment links, recurring plan setup, collection status, or open payment workflow.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Source links | Account, Contact, Sales Order, Invoice, Quote, Related Sales Order Number, Invoice Number, PO Number, Order Source, Order Information. | Use to connect payment intent back to customer/order/invoice context. |
| Amounts | Requested Amount, Authorized Amount, Captured Amount, Refunded Amount, Balance Due, Merchandise Amount, Shipping Amount, Tax Amount, Credit Amount, Shipping Duty. | Use for collection, refund, and payment-order aging reports. |
| Status and collection | Status, Collection Status, Collections Enabled, Collection Method, Collection Attempt Count, Collection Hold Reason, Due Date, Days Overdue, Payment Aging Bucket, Last Collection Action On, Next Collection Action On. | Use for AR work queues and payment follow-up. |
| Payment route | Payment Gateway, Route Key, Split By Gateway, Payment Method, Payment Method Token, Payment Profile, Payment Method Label, Payment Token Label. | Use for route/token readiness and gateway mix. |
| Payment link and email | Payment Link Email Sent, Last Payment Link Email Sent On, Email Sent Count, Last Email Status, Last Email Type, Last Email Recipients, Last Email Error, Last Email Sent Date. | Use for payment-link follow-up and failed-email reports. |
| Transaction summary | Transaction Count, Last Transaction, Latest Transaction At, Latest Transaction Reference, Latest Transaction Method Label. | Use for current-state payment progress. Drill into transactions for exact attempts. |
| Recurring plan | Payment Frequency, Payment Count, Payment Start Date, Payment End Date, Payment Stop, Next Scheduled Payment, Recurring Transaction Count, Charge Date. | Use for recurring payment reporting. |
| Billing/shipping snapshots | Billing and shipping name/address/phone/email fields, billing/shipping address trackers. | Use for historical payment evidence. Do not treat as current Account address. |
| Idempotency and imports | Idempotency Key, Raw Payload Hash, Migration Batch Key, External Source *, Metrics Last Calculated At, Metrics Version. | Use for audit/debugging, not normal business filters. |
Best practice: Payment Order reports are for "what are we trying to collect?" Use Payment Transaction reports for "what actually happened?"
Payment Transaction
Payment Transactions are processor/payment action evidence. Use them for failed charges, captures, refunds, voids, settlement, gateway accounting, and payment method analysis.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Source links | Payment Order, Sales Order, Invoice, Quote, Related Sales Order Number, Invoice Number. | Use to drill from payment evidence back to source records. |
| Status/action | Status, Transaction Action, Entry Mode, Manual Payment Type, Effective Date, Processed At, Processed Amount, Requested Amount. | Use for transaction outcome and action-type reports. |
| Balances | Balance Due Before, Balance Due After, Merchandise Amount, Shipping Amount, Tax Amount, Credit Amount, Fee Amount, Net Amount. | Use for accounting and reconciliation. |
| Gateway/provider evidence | Payment Gateway, Provider Transaction Id, Provider Reference Id, Provider Credential Version, Vault Gateway Key, Vault Transaction Id, Reference Number. | Use for processor/gateway reconciliation. |
| Failure evidence | Failure Code, Failure Message. | Use for failed-transaction exception reports. |
| Settlement | Settlement Batch, Settlement Status, Settlement Reference, Settled On, Last Settlement Synced On, Settlement Sync Status, Settlement Sync Message. | Use for settlement and accounting reports. |
| Payment method snapshot | Payment Method, Payment Method Token, Payment Method Label, Payment Token Label, payer fields. | Use for payment method mix without exposing sensitive card data. |
| Recurring fields | Payment Frequency, Payment Count, Payment Start Date, Payment End Date, Next Scheduled Payment, Recurring Transaction Count. | Use for recurring plan transaction reporting. |
| Idempotency and imports | Idempotency Key, Execution Key, Raw Payload Hash, External Source *. | Use for debugging, replay prevention, and migration audit. |
Best practice: never create fake transactions to make a report balance. Transactions should reflect real processor/manual payment events.
Payment Method And Token
Payment Method is the customer-facing saved method. Payment Method Token is gateway-route token coverage.
| Object | Important fields | How to use in reports |
|---|---|---|
Payment_Method__c | Account holder, assigned contact, display name, method type, brand, last4, expiration, default flag, status, tokenization source, tokenized on, payment gateway, reusable across gateways, account updater fields. | Use for saved-method inventory and customer payment readiness. |
Payment_Method_Token__c | Payment method, payment gateway, status, token type, token scope, gateway default flag, provider token reference, provider profile ids, last validated date, account updater status. | Use for gateway/token coverage and retokenization readiness. |
Best practice: a customer can have one visible saved method but multiple gateway tokens. Use token reports when the question is route readiness.
Payment Receipt
Payment Receipts are collected-funds evidence.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Source links | Account, Contact, Sales Order, Invoice, Payment Order, Payment Transaction, Payment Intent, Quote. | Use to trace collected money back to the source. |
| Amounts | Amount, Fee Amount, Net Amount, Unapplied Amount. | Use for receipt, unapplied funds, and settlement reporting. |
| Receipt details | Receipt Date, Received On, Receipt Method, Receipt Type, Reference Number, Status, Settlement Reference. | Use for payment receipt trend and reconciliation. |
| Payer/link | Payer Display Name, Payer Handle, Payment Link URL. | Use for audit/detail reports. |
| Email evidence | Email Sent Count, Last Email Status, Last Email Sent Date, Last Email Recipients, Last Email Error. | Use for receipt email coverage. |
Best practice: use receipts when the question is "what money was received?" Use transactions when the question is "what processor action occurred?"
Invoice
Invoices are receivable documents tied to Accounts and Sales Orders.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Source/customer | Account, Contact, Sales Order, Customer PO, billing address fields. | Use for invoice lists and customer follow-up. |
| Dates and terms | Invoice Date, Due Date, Payment Terms, Days Overdue, AR Aging Bucket. | Use for aging and collections. |
| Amounts | Subtotal, Tax Total, Shipping Amount, Discount Amount, Total Amount, Amount Paid, Balance Due. | Use for invoice AR and payment progress. |
| Status and email | Status, Payment Link, Email Recipients, Email Sent Count, Last Email Status, Last Email Sent Date, Last Email Error. | Use for invoice lifecycle and email exception reports. |
| Migration lineage | External Source Key. | Use for reconciliation only. |
Best practice: use Invoice reports for receivable documents and due dates. Use Sales Order fields for operational order state and Payment fields for actual money movement.
Common Payment Reports
| Report | Base object | Filters | Key fields |
|---|---|---|---|
| Payment links not sent | Payment Orders | Payment-link sent false or last email status failed. | Account, Sales Order, Balance Due, Due Date, Last Email Error. |
| Failed payment attempts | Payment Transactions | Status failed/declined or failure code present. | Payment Order, Gateway, Transaction Action, Processed Amount, Failure Code, Failure Message. |
| Settlement reconciliation | Payment Transactions | Settlement date/status range. | Gateway, Provider Transaction Id, Settlement Batch, Settled On, Fee Amount, Net Amount. |
| Open invoices | Invoices | Balance Due > 0. | Account, Sales Order, Due Date, Days Overdue, Balance Due. |
| Token coverage | Payment Method Tokens | Status and gateway filters. | Payment Method, Gateway, Token Scope, Last Validated On, Status. |
Last updated on