This guide outlines the steps required to enable Ledger Sync for a customer location and how to QA the data once onboarding is complete.
✅ Step 1: Add to Product Group
Manually add the location to the appropriate Product Group in Tools.
📌 This is the step that officially enables the feature and initiates the onboarding workflow.
🔄 Step 2: Await Automated Onboarding
Enabling the feature triggers the automated onboarding process.
Here’s what happens next:
A sync command is automatically generated to fully backfill the location’s ledger data.
This sync runs overnight to avoid impacting regular operations.
You can monitor onboarding progress from the Onboardings tab in Tools.
🔍 Step 3: QA Balances
Once onboarding is marked complete, perform a quick sanity check:
Check the Web app's total outstanding balance.
Cross-reference with Sigma dashboards (Ledger Balances, etc.).
If something looks off, investigate sync logs
We can now view balance accuracy in tools.
Go to Tools > search institution > select balance accuracy under Ledger Sync > click Actions > run full audit > click refresh.
If its under 1.5% then good to go, if its above then either need to escalate or follow troubleshooting steps to fix
There are buttons within the Actions meny that you can try to run if balance mismatch is off.
If those don't work, create a JIRA ticket.
📝 Required Information for the JIRA Ticket (if escalation is needed):
Title: Clear summary (e.g., “Balance discrepancy – ABC Dental”)
Institution / Location / Datasource ID(s)Unique identifiers related to the issue
Reported IssueIs the balance not showing, incorrect, or delayed?
Specific ExamplesInclude patient IDs with:
• Expected balance amount
• Actual balance shownScreenshotsProvide screenshots from the EHR showing actual ledger dataTags
Add the following tags to the ticket:
• ledger-sync
• cs-escalation
Reference Example: Example Ticket – SAAS-12930
✅ Best Practices:
Double-check the patient ID and ensure it’s linked to the correct datasource.
Provide as much detail as possible to help engineering quickly triage and resolve.
Use the correct Jira board: PAY (not SAAS or OPS unless directed).