Relationship Commerce, receivables, and payables
Use one Relationship as the commercial context for a customer, supplier, breeder, transporter, or other external party and review linked sales, purchases, invoices, bills, payments, animals, balances, and activity without creating parallel contact records.
Before you begin
- Business tools are enabled in Settings → Experience & Features.
- You have an owner, administrator, or manager role for sensitive commerce data.
- The correct Relationship exists and duplicate contacts have been reviewed.
- Sales and purchasing source records are linked to that Relationship where applicable.
Interface walkthrough
These annotated interface maps describe the current PMA controls. They do not replace a real record review in your workspace.
Shows the commercial history and current balances tied to the selected Relationship.
Shows organization-wide customer receivables and supplier payables with due-date aging.
Open the authoritative source record rather than re-entering the same transaction elsewhere.
Step-by-step workflow
Use one Relationship identity
Assign all appropriate roles to the same person or organization instead of creating separate customer and supplier identities for the same counterparty.
Review the commerce summary
Compare lifetime sales and purchases with current receivable and payable balances, then inspect the linked source records.
Review due balances
Open Receivables & Payables to see Current, 1–30, 31–60, 61–90, and 90+ day aging based on the recorded due date.
Follow the source trail
Move from a payment or balance back to the invoice or supplier bill, order, and Relationship. Use Income & Expenses for cash-movement reporting.
Keep commercial and husbandry meaning separate
A commercial Relationship can also be a breeder, veterinarian, transporter, or animal source. Preserve all relevant roles on the same record.
Expected result
The Relationship becomes the durable commercial context while sales orders, purchase orders, invoices, bills, payments, animal links, and financial entries remain authoritative in their own systems.
Safety boundaries
- Experience visibility does not grant permission; sensitive commerce remains role protected.
- Receivable and payable aging is operational follow-up, not a substitute for an accountant or formal general ledger.
- Do not merge Relationships solely because names are similar.
- Use source documents and actual payment records when resolving discrepancies.
Troubleshooting
Commerce is missing from a Relationship
Confirm Business tools are enabled, your role has business access, and the source sales or purchase record is actually linked to this Relationship.
A balance appears in the wrong aging bucket
Review the invoice or supplier bill due date. Aging uses that recorded due date relative to the current date.
The same company appears twice
Review Relationship duplicates and source links before creating more records. A single Relationship can hold multiple roles.