Skip to main content

Overview

You build a Statement in the Statement Manager, a single screen where you search for eligible Orders, link them to the Statement, and set the Statement’s own details (Business Unit, Statement Date, Payment Term, and more). You reach the Statement Manager from the Create Statement quick action on an Account or Contact, or from the Manage quick action on an existing Statement.

Prerequisites

  • The Create Statement quick action is on the Account and Contact page layouts, and Manage is on the Statement page layout — see Configuring Statements.
  • You have a permission set that grants access to the Statement object and its fields. See Configuring Statements.

Creating a Statement from an Account or Contact

1

Open the Statement Manager

On an Account or Contact record, click Create Statement.fusionCore pre-fills the new Statement from the record you started on: the customer type, the Account and/or Contact, the billing Contact, and the customer’s address. The Statement Date defaults to today. If your org uses multiple currencies and the FC_Use_Customer_Currency_New_Statement constant is enabled, the Statement also defaults to the customer’s currency.
2

Search for and link eligible Orders

Use the search filters — order number, customer type, order status, Business Unit, Account/Contact, effective date range, balance range, and currency — to find Orders to add, then link the ones you want on the Statement.An Order is eligible to link only when it has a balance due greater than zero, or a balance of zero and a Status of Activated (a paid Order you still want to close out on the Statement). Orders already locked to a different Statement that prevents individual payment are excluded from the results. The search returns at most 200 Orders at a time — narrow your filters if you don’t see the Order you’re looking for.
3

Open Statement Settings

Click Statement Settings to set the Statement’s own fields — Business Unit, Statement Date, Payment Term, address (or an address override), and the Prevent Paying On Orders toggle.
4

Save

Click one of the three save options:
  • Quick Save — saves without leaving the Statement Manager.
  • Save and Exit — saves and returns you to the record you started from.
  • Save and Proceed to Payment — saves and takes you straight to the payment screen.
A newly saved Statement defaults to Draft status.
Clicking New from the Statement tab opens Salesforce’s standard record-create dialog, not the Statement Manager. Use the Create Statement or Manage quick action to reach the Statement Manager.

Editing a Statement

Click Manage on a Statement to reopen it in the Statement Manager. Manage is only available while the Statement is in Draft or Open status — these are the only statuses where you can link or unlink Orders, change Statement Settings, or toggle Prevent Paying On Orders. Once a Statement moves to Pending Payment or beyond, most of these fields lock; see Statement Statuses for exactly what freezes and when.

Linking and Unlinking Orders

The Statement Manager blocks a link or unlink and shows an explanatory message when: An Order with active installments also can’t be added to a Statement that has Prevent Paying On Orders enabled. To proceed, uncheck Prevent Paying On Orders on the Statement, or cancel the installments on the Order.

Prevent Paying On Orders

Prevent Paying On Orders locks every Order linked to the Statement so it can only be paid through the Statement — a staff user or Portal member can no longer pay that Order directly. fusionCore records the lock on the Order’s FCORE_PAY__Payment_Statement__c field. You can only change this toggle while the Statement is Draft or Open. What happens when you turn it on depends on whether the linked Orders are shared with other Statements, and on which surface you’re using:
  • Editing the field directly on the Statement record is blocked outright when a linked Order is also on another active Statement: Cannot enable Prevent Paying On Orders: one or more linked Orders are also linked to other Statements. Unlink them from the other Statements first.
  • The Statement Manager instead offers to resolve the conflict for you: The following orders are linked to other statements. To enable Prevent Paying On Orders, they will be unlinked from those statements. Do you want to continue? Confirming unlinks the shared Orders from the other Statements and enables the toggle.
Locking and unlocking an Order runs asynchronously. After you enable or disable Prevent Paying On Orders, give it a moment and refresh the Order before you check whether the lock took effect.

Limitations and Common Pitfalls with Statement Creation

  • Link/unlink and settings only work in Draft or Open. Once a Statement advances past Open, use Statement Statuses to move it back before you can change its Orders or settings again.
  • The order search caps at 200 results. If the Order you expect isn’t showing, narrow the filters rather than assuming it’s missing.
  • Currency locks in once Orders are linked. You cannot change a Statement’s currency after it has linked Orders.
  • Draft Statements are deleted automatically after 30 days. An unfinished Draft with no financial activity is cleaned up by a scheduled job unless you check Prevent Automated Deletion on it. See Configuring Statements.
  • Always set the Statement’s customer before taking payment. A Statement cannot enter Open or Pending Payment status without both an Account and a Contact set, but a Draft Statement can still be paid even without one. Set the customer first to avoid a payment recorded against a Statement with no customer on it.