What is the difference between a SubAccount and a Goal?

From a practical perspective, a SubAccount and a Goal are the same — both are simply a form of Account within the Helix model.

Why should a Customer have a primary account?

On the account object, the isPrimary property designates the primary account for a customer. In business models that permit multiple accounts, SubAccounts, or Goals, this account must remain open for as long as the Customer is active. This requirement stems from the regulatory and legally permitted flow of funds models governing Goals and SubAccounts.

Common Mistake #1: Not using Helix as System of Record for SubAccounts

Failing to use Helix to track Goals or SubAccounts disrupts the flow of funds. The scenarios below walk through some common examples.

📘
Scenario Background:
Alex downloaded a new Goal-based savings application called "Beta One" that provides a monthly 1% loyalty reward. After registering, Alex is prompted to create multiple Goals and sets up three, each expiring at the end of the month:

Goal 1 — Christmas Savings, with a recurring contribution of $200 at the end of each month

Goal 2 — End of Month Party, with a funds transfer every time he visits Starbucks

Goal 3 — End of Week Grocery Bill, which he will manually move funds into daily

Scenario 1: Goal closure for in-process sweep payments

Alex closes out Goal 1 and Goal 2. Legally, Alex is now entitled to a dollar amount. However, without a primary account there is no way to identify which account should receive the funds.

Scenario 2: Developer didn't use Helix as System of Record

Alex's three Goals are managed at the application level rather than in the Core. When a $500.00 deposit arrives to Helix, a financial gap opens between what the System of Record reflects and what Alex sees in "Beta One."

Scenario 3: Alex's Goal 3 is closed by the bank

A fintech partners with a bank to deliver banking functionality. The bank has the right — and in some scenarios the obligation — to close accounts on behalf of a fintech's customer. When Goal 3 is closed and the funds are returned to Alex's External Account, what balance should "Beta One" display to Alex?

Common Mistake #2: Data freshness and account state

Account balances, beneficiaries, and transactional data can all change outside your application — a bank partner has the right, and sometimes the obligation, to modify or close an account on a customer's behalf. Showing a customer a stale balance isn't just an architecture concern; in regulated financial products, it's a compliance one.

Helix is the system of record for all product data used in the API. Always fetch balance and account data live from Helix, and let your developers focus on building your product — Helix handles balance tracking, incoming bank files, transaction processing, and the data requirements for participating in financial markets.