Connect Stripe to Sanka and configure invoice import, subscription import, and payment reconciliation.
Last updated: May 29, 2026
Set up Stripe with Sanka so you can import Stripe invoices and subscriptions into Sanka, manage billing records, and reconcile paid invoices with payment records. Start with test keys, validate the import result, then switch to live keys once your operating rules are confirmed.
Prerequisites
Stripe API keys (test/live) and a Stripe account with the required permissions.
Sanka workspace admin access.
A customer handling rule for imported Stripe invoices. Decide whether invoices should use each Stripe customer or be grouped under one fixed customer such as Stripe Customer.
An operating rule for reviewing payment records and invoice allocations after importing paid Stripe invoices.
A policy for fees and FX differences. Decide whether to use adjustment lines or handle them in accounting.
Sample prompt
/sanka Review this Stripe import plan before making any changes. Confirm the Stripe account, test or live key, invoice or subscription scope, customer resolution mode, fixed customer if used, paid invoice behavior, payment allocation, fees and FX handling, and any action or workflow that should run after import. Do not import live records, create payment links, or update invoices until I approve the plan.
Connect
In Sanka, open Workspace > Integrations.
Select Create integration, then choose Stripe.
Enter the Stripe API key. Use a test key for the first validation run.
Confirm Stripe appears in the integration list, then share access with the teammates who need it.
Sync settings and import rules
Invoice import creates or updates Sanka invoices from Stripe invoices. Sanka stores the amount, amount excluding tax, currency, due date, Stripe invoice URL, and original Stripe customer details.
Stripe invoices with paid status are imported as paid invoices in Sanka. Sanka also creates a payment record and allocates it to the invoice. Stripe invoices that are not paid are imported as drafts.
For customer handling, choose whether to use each Stripe customer or group invoices under one fixed customer such as Stripe Customer. Use a fixed customer when you want to group payments and accounting review by Stripe as a payment platform.
If the same Stripe invoice or subscription is imported again, Sanka updates the existing record. The import drawer does not provide a separate "create only" versus "create and update" mode.
Fees and FX differences are not automatically added as adjustment lines during invoice import. Compare Stripe payout reports with Sanka payments and invoices, then make any required accounting adjustments separately.
Import Stripe invoices
In Sanka, open Commerce > Invoices.
Select Import.
Set Import source to Integration, then choose the Stripe integration in Integration.
Choose Customer Resolution Mode.
Use Stripe customer: Sanka looks for a matching company or contact for each Stripe customer and creates one when needed. Use this when you want receivables managed by the original customer.
Use fixed customer: Sanka creates all imported Stripe invoices under the selected fixed customer. Use this when Stripe should be treated as one payment platform customer so payments and accounting entries are easier to group.
If you choose Use fixed customer, select the company or contact in Fixed Customer. If there are no available options, create a company or contact such as Stripe Customer first.
Property mapping is not required for Stripe invoice import. Review the selections, then click Import records.
Imported invoices keep source details such as the Stripe invoice ID, invoice number, status, currency, and invoice URL. When you use a fixed customer, the original Stripe customer ID, name, and email are also kept in the source details for audit and support review.When a Stripe invoice is already paid, Sanka also creates a payment record and allocates it to the imported invoice. After the import, open Payments and confirm the amount, currency, payment date, and invoice allocation.
Import Stripe subscriptions
In Sanka, open Commerce > Subscriptions.
Select Import.
Set Import source to Integration, then choose the Stripe integration in Integration.
Property mapping is not required for Stripe subscription import. Review the selections, then click Import records.
The import brings Stripe subscription ID, customer, status, amount, currency, start date, next billing date, billing frequency, and line items into Sanka subscriptions. If the same Stripe subscription has already been imported, Sanka updates information such as the billing interval on the existing record.
Validate the setup
With test keys, create a small test invoice in Stripe, then import invoices in Sanka.
Import a Stripe invoice with paid status, then confirm the Sanka invoice is paid and a payment allocation appears in Payments.
If you use a fixed customer, confirm invoices from multiple Stripe customers are linked to the same fixed customer in Sanka.
Import Stripe subscriptions, then confirm customer, status, billing frequency, next billing date, and line items.
When fees or FX differences exist, compare Stripe payout reports with Sanka payments and invoices, then apply your accounting rule for the adjustment.
Review after import
In Invoices, confirm the customer, status, amount, due date, and Stripe invoice URL.
If you used a fixed customer, confirm that invoices from multiple Stripe customers are grouped under the same Sanka customer.
In Payments, confirm the payment record and invoice allocation.
In Subscriptions, confirm the customer, status, next billing date, line items, and billing frequency.
In the Import history, check the success and failure counts. If there are failures, review the Stripe record and the error detail.
Troubleshooting
Stripe is connected but invoices or subscriptions are missing
Confirm the selected Stripe integration, test or live key, import scope, and whether the target records exist in the connected Stripe account. If you recently switched keys, confirm that the records are in the same Stripe mode as the key you entered in Sanka.
Paid Stripe invoices did not create payment allocations
Check that the Stripe invoice status is paid, then review the imported Sanka invoice, payment record, currency, amount, and allocation. If the invoice was imported as a draft or under a different customer, review the customer resolution mode before rerunning the import.
The wrong customer was used
Review whether the import used each Stripe customer or one fixed customer. If the wrong mode was used, inspect existing Sanka invoices and payment allocations before reimporting, because reruns update existing records rather than creating a separate create-only batch.
Fees or FX differences do not match accounting
Stripe fees and foreign-exchange differences are not automatically added as invoice adjustment lines during import. Compare Stripe payout reports with Sanka invoices and payments, then apply the accounting rule your team chose for adjustments.
A payment link, subscription link, or hosted invoice cannot be created
Confirm the Stripe integration is connected, the selected order or subscription has the required amount, currency, customer, and line-item details, and the field used to store the link exists. If Stripe Connect onboarding is required, complete it before creating hosted invoice links.
Checkpoints
Use Sanka invoices, subscriptions, payments, import history, action history, workflow history, and audit logs to confirm Stripe behavior before replying to a customer or asking AI to make a code change.
Search Sanka...
Review Stripe integration activity
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
3Reviewed Stripe import setup2026/05/10 14:00Stripe invoice importChecked live mode, fixed customer, and paid invoice behaviorClaude integration
1Checked accounting adjustment2026/05/10 14:30Stripe payout reviewCompared Stripe fees with Sanka payment and invoice recordsSanka user
A safe review should include the Stripe account, test or live mode, imported invoice or subscription, customer resolution mode, payment allocation, fees or FX policy, and any downstream action or workflow.
Go-live tips
Before switching to live keys, run one invoice import and one subscription import with test keys.
Decide whether invoices should use a fixed customer before the first import. If you change the mode later, review existing invoices and payment allocations first.
During the first week after go-live, check import history, invoice balances, and payment allocations daily. If discrepancies appear, revisit the customer resolution mode and accounting rules.
Imported invoices keep source details such as the Stripe invoice ID, invoice number, status, currency, and invoice URL. When you use a fixed customer, the original Stripe customer ID, name, and email are also kept in the source details for audit and support review.
When a Stripe invoice is already 
The import brings Stripe subscription ID, customer, status, amount, currency, start date, next billing date, billing frequency, and line items into Sanka subscriptions. If the same Stripe subscription has already been imported, Sanka updates information such as the billing interval on the existing record.
