Finance and Commission Object Fields

Field guide for GL accounts, item GL defaults, financial audits, and commission configuration reporting

Finance and commission reports should distinguish setup records from result fields. Setup objects explain why a result should happen. Sales Order and Sales Order Line fields show what was calculated on actual orders.

GL Account

GL Accounts define posting destinations for revenue, inventory, COGS, expenses, and variance.

Field	Use in reports
`Account Number`	External/accounting code used for reconciliation.
`Account Type`	Revenue, asset, expense, liability, equity-style classification.
`Account Subtype`	More detailed finance classification.
`Normal Balance`	Debit/credit expectation for finance review.
`Active`	Whether the account should still be used.
`Posting Allowed`	Whether automation should post to the account.
`Parent Account`	GL hierarchy and rollup grouping.
`External ERP Key`	ERP/accounting-system mapping.

Best practice: use GL Account reports for chart-of-accounts readiness. Use item/order reports for transaction impact.

Item GL Account Default

Item GL Account Defaults resolve missing GL fields on Items automatically.

Field family	Important fields	How to use in reports
Rule selection	`Rule Type`, `Product Type Value`, `Category Value`, `Priority`, `Active`.	Use to understand which defaults will apply first. Lower priority numbers apply earlier.
Output accounts	`Revenue GL Account`, `Inventory GL Account`, `COGS GL Account`, `Expense GL Account`, `Inventory Expense GL Account`, `PWO Material Variance GL Account`.	Use to audit item setup coverage.

Best practice: do not manually maintain one-off item GL fields when a default rule should cover the category or product type. Use GL Intelligence/admin repair paths where available.

Sales Order Financial Audit

Financial Audit records preserve evidence after payment, fulfillment, email, or post-baseline order changes.

Field family	Important fields	How to use in reports
Order/customer snapshot	`Sales Order`, `Related Sales Order`, `Account`, `Sales Rep`, `Order Total`, account channel/business classification, revive/upsell fields.	Use to understand the order context when audit started.
Audit lifecycle	`Audit Status`, `Audit Creation Source`, `Audit Start Date`, `Latest Audit Refresh`, `Last Change On`, `Audit Key`.	Use for audit queue and stale audit reports.
Baseline detail	`SKU Snapshot`, `Credit Item Summary`, `Shipping Item Summary`, original credit/shipping total fields.	Use for before/after evidence.
Change totals	`Adjustment Count`, `Credit Adjustment Total`, `Net Adjustment Amount`.	Use to measure post-baseline changes.
Payment evidence	first payment activity/approved payment dates, primary Chargent order, Chargent order count, gateway summary, multiple Chargent flag.	Use for payment-related audit review and legacy Chargent context.
Email evidence	email timeline, failed email types, received email types, all attempted emails succeeded.	Use for customer-communication audit.

Best practice: do not delete or ignore audit records because they look like logs. They are finance-control evidence.

Sales Order Audit Change And Audit Line

Use audit change/line records when the question is about exactly what changed after the financial baseline.

Object	Use
Sales Order Audit Change	Header-level change evidence: who/what/when and financial impact.
Sales Order Audit Line	Line-level change evidence for SKU, quantity, price, credit, shipping, or cost changes.

Best practice: use the Financial Audit header to find orders needing review, then drill into audit changes/lines for exact adjustments.

Commission Configuration

Commission Configuration records describe legacy/fallback commission rules and scoped overrides.

Field family	Important fields	How to use in reports
Scope	`Configuration Type`, `Item`, `Item Group`, `Commission Group`, `Customer Org`, `Sales Rep`, `User`.	Use to understand which items/customers/users a rule applies to.
Lifecycle	`Active`, `Effective Date`, `Expiration Date`.	Filter active/inactive/current rules.
Description	`Configuration Name`, `Notes`.	Use for admin review and cleanup.

Best practice: Commission Configuration is setup. To report actual commission results, use Sales Orders or Sales Order Lines.

Commission Rate

Commission Rate records define tier rows under a commission configuration.

Field family	Important fields	How to use in reports
Tier identity	`Tier Name`, `Sort Order`, `Active`, parent Commission Configuration.	Use for tier inventory and rule review.
Price/quantity criteria	`Price Threshold`, `Unit Price`, `Price Tolerance`, `Min Units`, `Max Units`, `Pricing Column`.	Use to explain why a line matched a tier.
Result	`Commission Rate %`.	Use for setup reporting.
Review flag	`Requires Management Approval`.	Use for rates that require approval before payout confidence.
Legacy customer scope	`Customer Tier`.	Use only where fallback migration logic needs it.

Best practice: tier reports should include active status and effective/expiration context from the parent configuration.

Commission Group, Tier, And Member

These objects support the newer group/tier engine.

Object	Important fields	How to use in reports
`Commission_Group__c`	Default pricing mode, description, active flag, SKU count.	Group-level setup and coverage.
`Commission_Group_Member__c`	Commission group, item, SKU code, active flag.	Which SKUs belong to which commission group.
`Commission_Tier__c`	Commission group, tier name, default commission %, price/quantity/monthly spend criteria, pricing column, approval flag, active flag, sort order.	Active tier ladder and payout rule review.
SKU/user override objects	Item/user-specific override scope, effective values, active state.	Exception reporting for commission calculations.

Best practice: use Commission Group/Tier reports to explain setup. Use Sales Order Line commission fields to explain what happened on a transaction.

Transaction Result Fields

Actual commission results usually live on Sales Orders and Sales Order Lines.

Object	Key fields
Sales Order	`Total Commission Amount`, `Average Commission Rate`, `Commission to Margin Ratio`, `Commission to Revenue Ratio`, `Net Margin After Commission`, `Net Margin % After Commission`, `Order Profitability Tier`.
Sales Order Line	`Commission Amount`, `Commission Rate Percent`, `Calculated Commission Rate`, `Commission Status`, `Commission Tier`, `Matched Tier Name`, `Commission Source`, `Commission Resolution Path`, override flags, approval fields, split fields.
Quote Line	Similar commission preview fields before order conversion.

Best practice: payout-readiness reports should include payment status, collected amount, refunds/disputes if relevant, commission status, and margin after commission. A high commission total by itself is not payout readiness.

Finance Report Patterns

Report	Base object	Filters	Key fields
Items missing GL setup	Item	Any GL field blank, active/sellable items only.	SKU, Item Group, Product Type, Item Category, missing GL fields.
GL default coverage	Item GL Account Defaults	Active rules.	Rule Type, Product Type Value, Category Value, priority, output accounts.
Financial audit queue	Sales Order Financial Audit	Audit status open/review.	Sales Order, Account, Sales Rep, Net Adjustment Amount, Last Change On, failed email types.
Commission setup review	Commission Group/Tier/Rate	Active rules.	Group, tier, rate, pricing column, min/max criteria, approval flag.
Actual commission by rep	Sales Orders or Sales Order Lines	Date/payment status filters.	Primary rep, total commission, collected amount, margin after commission, commission status.

Avoid These Mistakes

Mistake	Why it breaks reports
Reporting payout from setup objects.	Setup objects show rules, not earned commission.
Ignoring payment status in commission reports.	Uncollected or disputed orders may not be payout-ready.
Editing item GL fields without reviewing defaults.	The same gap can reappear on the next item unless the default rule is fixed.
Treating financial audit as disposable log data.	It preserves post-baseline finance evidence.
Looking only at order header commission totals for item issues.	Line-level commission fields explain which item/rule caused the result.

On this page