Skip to main content
Helcim closes a batch of card sales once a day and deposits it a few days later, sometimes two batches as one deposit, and takes its fees from the bank separately. Zeno reads the batches from Helcim and records them the way a bookkeeper would, through a clearing account, so every sale, deposit and fee lands where it should and clearing returns to zero. Helcim works with QuickBooks Online books.

The result: each batch’s sales booked on the day it closed, each Helcim deposit matched to the batches it carried, and each fee on its own line.

​
Connect Helcim

Helcim has no sign-in to send you to. You make a token in Helcim and paste it into Zeno.
1

Make a token in Helcim

In Helcim, open All Tools → Integrations → API Access Configurations and create a token. Give it read access to transactions and nothing else: Zeno only reads.
2

Paste it on Connections

Under Clients → Connections, pick the client, paste the token on the Helcim card, say whether the account deposits in US or Canadian dollars, and press Connect Helcim. Zeno tries the token once before saving it, keeps it sealed, and never shows it again.
3

Choose where the money goes

Once per client: the bank account Helcim deposits into, the clearing account batches wait in (an Other Current Asset, never the bank itself), and accounts for sales, refunds and Helcim’s fees. Choose them on the Helcim card, or ask your AI to set them from the client’s chart.

​
What Zeno reads

New batches and their transactions several times a day, unattended, going back 90 days on the first read. A batch is ready once its transactions add up to Helcim’s own total for it; one that does not is read again and never guessed at. To read sooner, ask your AI to sync.

​
How it is recorded

Zeno holds a deposit back, and says why, when no run of batches adds up to it, or when the batches it carries are not in clearing yet. Lines the register already has are held too, until a person has looked.

​
Plan them

Ask your AI to plan the client’s Helcim activity. The batches, deposits and fees waiting become one plan. Nothing posts until a person approves it.

​
Disconnect

Disconnect on Connections makes Zeno forget the token and stop reading. Batches already read and anything posted stay. Delete the token in Helcim too if nothing else uses it.