Account Billing
Account Billing is FlexiBill's auto-debit engine — designed for businesses that provide ongoing services and need to charge customers automatically at regular intervals. Instead of requiring customers to manually settle an invoice every billing cycle, Account Billing securely stores their payment method once and charges them on schedule without any customer action.
This makes payments effortless for the customer and ensures your business collects revenue on time, every cycle.
What Is Account Billing?
Account Billing is a complement to Subscription and Billing — and can also be used as a standalone auto-debit solution independently of the subscription engine.
With Subscription and Billing
Use Subscription and Billing to manage plans, pricing, and invoice records, then layer Account Billing on top to execute the actual charge automatically each cycle — so customers never need to click a payment link.
Without Subscription and Billing
Use Account Billing directly to register customer payment methods and execute recurring charges on schedule — without any invoice or subscription structure. Ideal when you manage billing logic in your own system and only need DOKU to execute the charge.
Subscription and Billing issues invoices that customers pay manually via a payment link. Account Billing charges the customer's registered card or bank account automatically — no customer action required after initial registration. Use them together or independently depending on your billing workflow.
Two Scheduler Models
DOKU Hosted Scheduler
A fully automated billing orchestration model where DOKU manages the entire charge execution lifecycle. Merchants register customer card details once, and DOKU handles all subsequent scheduling and payment processing automatically.
No need to manage customer token data storage on the merchant side
Schedule fully managed and executed by DOKU
One-time centralized data synchronization between merchant platform and DOKU ecosystem
Real-time registration and payment status callbacks
Set it once. DOKU charges automatically on schedule.
Merchant Hosted Scheduler
A merchant-controlled billing model where the merchant manages their own customer token data and triggers payment execution on demand. Gives merchants full control over when and how charges are initiated.
Merchant manages customer token data storage internally
Merchant defines and controls the billing schedule
Supports bulk billing orchestration via file upload (SFTP or Dashboard)
Suitable for data-driven, internally controlled billing workflows
You own the schedule. DOKU executes the charge.
Features & Benefits
💳 Automatic Charging — Set and Forget
Once a customer's payment method is registered, charges are processed automatically on the configured schedule — daily, weekly, or monthly — without any manual trigger from the merchant or the customer.
🔒 Secure Card Tokenization
Customer card details are stored using industry-standard PCI-DSS compliant tokenization managed entirely by DOKU. Sensitive card data — card numbers, CVVs, expiry dates — never touches the merchant's server. Merchants work with secure tokens only.
📊 Real-Time Payment Tracking
Monitor payment statuses, success rates, and failed charge attempts in real time from the Account Billing dashboard. Always know which customers have been charged and which have not.
⚡ High-Volume Batch Processing
Process large volumes of recurring payments simultaneously via bulk file upload through SFTP or the DOKU Dashboard — ideal for businesses with thousands of active customers in a single billing run.
💰 Steady and Predictable Cash Flow
Automated charging removes payment friction — customers no longer need to remember to pay, reducing late payments and churn caused by missed invoices.
🔁 Flexible Billing Cycles
Supports daily, weekly, monthly, and annual billing cycles — configurable to match any subscription or service model.
How It Works
How Billing Dates Work
Account Billing uses calendar-based scheduling — charges are anchored to a fixed day of the month (e.g., the 5th or the 20th), not a relative interval from when the customer registered. Every customer assigned to a billing date is charged on that specific calendar date each cycle.
This is a fundamental difference from Subscription and Billing's interval logic:
Scheduling model
Calendar-based — fixed day of the month
Interval-based — relative to subscription start date
Example
All customers on the 5th are charged on the 5th of every month
A subscription starting on the 18th renews on the 18th each month
When customers are charged
On the configured billing date, regardless of when they registered
On the anniversary of their own start date
Proration
Not supported — first and all subsequent charges are the full amount
Not applicable
Best for
Batch-oriented billing where all customers settle on the same date(s)
Individual billing tied to each customer's own start date
Registration Mid-Cycle
When a customer registers on a date that is not their billing date — for example, they register on the 18th but the billing date is the 5th — the following happens:
The void charge on registration day is purely a card validation step. Customers will see a temporary authorization on their bank statement that disappears within a few business days — no money is actually deducted.
Multiple Billing Dates and Retry Logic
Each customer can be assigned their own billing date — merchants are not limited to a single billing date across their entire customer base. This flexibility also enables retry logic: a merchant can configure multiple consecutive dates for a single customer's billing cycle (e.g., the 5th, 6th, and 7th), so that if the charge fails on the primary date the system automatically retries on the next configured date.
If Send One Bill/Month is enabled in Bill Execution Preferences, only the first successful charge within a calendar month counts. All subsequent charge attempts in the same month — including retry dates — are automatically skipped once a successful charge has been recorded for that customer. This prevents double-charging when a customer is successfully charged on a retry date.
No Proration
Account Billing currently does not support proration. Customers who register mid-cycle are always charged the full billing amount on their first billing date, regardless of how many days remain between their registration date and that first charge. If your business model requires prorated first charges, this must be handled outside of Account Billing.
Scheduler Comparison
Scheduling control
Fully managed by DOKU
Merchant-defined, on-demand
Token management
DOKU stores and manages tokens
Merchant manages tokens internally
Data flow
One-time sync, DOKU handles the rest
Merchant uploads data per cycle
Best for
Real-time online registration flows
Bulk billing with internal data control
Primary Value add
Seamless ecosystem integration
Data-driven, internal execution control
Touch points
API, Back Office (no-code)
API, Back Office (no-code), SFTP
Use Cases
Description
A SaaS platform needs to automatically charge customers a monthly or annual software subscription fee without requiring them to log in and pay each cycle.
Solution
Use DOKU Hosted Scheduler — customers register their card once during onboarding, and DOKU charges them automatically on the billing date each cycle. Combined with Subscription and Billing if an invoice record is required; used standalone if billing is managed in the SaaS platform itself.
How It Works
Customer registers card via API → DOKU tokenizes and stores credentials → charge executed automatically on schedule → success/failure notification sent to merchant.
Features Used
DOKU Hosted Scheduler, Credit Card Tokenization, Real-time Notification
Description
An insurance provider needs to collect quarterly or annual premium payments from thousands of policyholders on a specific calendar date.
Solution
Use Merchant Hosted Scheduler — the insurance system manages the billing schedule internally and triggers bulk payment execution via SFTP file upload on the designated date. Used standalone; no Subscription and Billing invoice is required.
How It Works
Merchant prepares billing file → uploads via SFTP → DOKU processes bulk charges on schedule → consolidated report generated for reconciliation.
Features Used
Merchant Hosted Scheduler, SFTP Batch Processing, Reporting
Description
A gym chain charges monthly membership dues for thousands of members automatically on the 1st of each month, and also issues an invoice for each member's records.
Solution
Use DOKU Hosted Scheduler layered on top of Subscription and Billing — Subscription and Billing manages the plan and invoice, and Account Billing executes the automatic charge so members are never required to pay manually.
How It Works
Member subscribes to plan (Subscription and Billing) → registers card at checkout → DOKU tokenizes card → on the 1st of each month, DOKU executes charge for all active members → invoice marked as paid automatically.
Features Used
DOKU Hosted Scheduler, Direct Debit, Subscription and Billing Integration
Description
A school wants to collect monthly tuition fees from hundreds of students via auto-debit, while also keeping invoice records for parents.
Solution
Use Merchant Hosted Scheduler combined with Subscription and Billing — the school manages the student roster and triggers charges each month via Dashboard file upload. Subscription and Billing generates the invoice record for each student.
How It Works
Students registered as members (Member Center) → subscription created per student (Subscription and Billing) → school uploads monthly charge file (Merchant Hosted Scheduler) → charges executed and invoices auto-marked as paid.
Features Used
Merchant Hosted Scheduler, Subscription and Billing, Member Center
Merchant & Customer Experience
Merchant View
Activate Account Billing and configure prerequisite payment channels (Credit Card RECURRING/MOTO or Direct Debit)
Choose DOKU Hosted Scheduler or Merchant Hosted Scheduler based on operational model
Register customer billing data via API, Dashboard (no-code), or SFTP file upload
Monitor payment status, success rates, and failed charges from the Account Billing dashboard
Configure Bill Execution Preferences — execution time window, duplicate charge protection, fraud filtering, and notification callback URLs
Customer View
Registers their card or bank account once during the initial checkout or onboarding flow
Receives a confirmation notification when their payment method is successfully registered
Is charged automatically on each billing date — no action required on subsequent cycles
Receives a payment confirmation notification after each successful charge
Terms & Conditions
Account Billing requires at least one compatible payment channel to be active on your DOKU account:
Credit Card with payment type SALE, RECURRING or MOTO, or
Direct Debit for automated bank account deductions
Contact your DOKU Account Manager to verify and activate the required payment channels before proceeding
Must be registered with a corporate business account on DOKU Dashboard
Business must be KYB (Know Your Business) verified on DOKU Dashboard
Account Billing Merchant Hosted Scheduler is available for Indonesian Business Accounts only
FAQ
What is the difference between Account Billing and Subscription and Billing?
Subscription and Billing is invoice-based — the system issues an invoice and the customer pays manually via a payment link each cycle. The customer is an active participant in every payment.
Account Billing is charge-based — the system charges the customer's registered card or bank account automatically on schedule. The customer registers once; all subsequent charges happen without their involvement.
How customers pay
Manually via payment link
Automatically charged — no action needed
Billing trigger
Invoice issued → customer pays
Card charged directly on schedule
Payment methods
Any DOKU-supported method
Credit Card (RECURRING/MOTO) or Direct Debit only
Best for
Invoice-based billing workflows
Seamless, invisible auto-debit
Can I use Account Billing without Subscription and Billing?
Yes. Account Billing works fully independently of Subscription and Billing. If your business manages billing logic in its own system and only needs DOKU to execute the actual charge against a stored card or bank account, you can use Account Billing standalone — without creating any collection, plan, or subscription in FlexiBill.
Can I use Account Billing together with Subscription and Billing?
Yes. This is the recommended approach when you need both invoice records and automatic payment collection. Subscription and Billing manages the plan, pricing, and invoice generation — Account Billing executes the automatic charge each cycle so the customer's invoice is settled without manual payment. The invoice is automatically marked as paid after a successful charge.
What is the difference between DOKU Hosted Scheduler and Merchant Hosted Scheduler?
DOKU Hosted Scheduler is a fully hands-off model — once customer data is registered, DOKU manages the schedule and executes all charges automatically. Best for real-time online onboarding flows where customers register directly.
Merchant Hosted Scheduler gives the merchant full control — the merchant manages customer token data internally and triggers charges on demand via API, Dashboard upload, or SFTP. Best for businesses with their own billing system that want to use DOKU only for charge execution.
What payment methods are supported for Account Billing?
Account Billing supports:
Credit Card — with SALE + RECURRING payment type (for subsequent recurring charges after an initial customer-present transaction) or MOTO (Mail Order Telephone Order, for charges processed without the customer being present)
Direct Debit — automated deductions from a customer's linked bank account after the initial mandate is established
Contact your DOKU Account Manager to verify which channels are available and active on your account.
What happens if a charge fails?
Failed charges are logged and the merchant receives a notification via the configured Payment Execution Notification URL (set in Bill Execution Preferences). The system supports retry logic and, if Freeze the Card is enabled, automatically bypasses cards previously flagged by the processor as Stolen, Frozen, or Restricted — avoiding unnecessary transaction fees on repeat failures.
Is customer card data stored on the merchant's server?
No. Customer card details are tokenized using PCI-DSS compliant vaulting managed entirely by DOKU. Sensitive data — card numbers, CVVs, expiry dates — never touches the merchant's server. Merchants work with secure tokens only, and DOKU handles all credential storage and security compliance.
What is the "Send One Bill/Month" setting?
When enabled in Bill Execution Preferences, this setting ensures that a customer is only successfully charged once per calendar month — even if multiple billing dates are configured. Any duplicate charge attempts within the same calendar month are automatically marked as ALREADY_PAID without hitting the bank, preventing accidental double-charges.
Does Account Billing support dynamic (usage-based) billing amounts?
Yes, via the URL Amount setting in Bill Execution Preferences. If the billing amount varies per cycle, you can configure an endpoint URL that the system queries just before each scheduled charge. The system uses the billing_amount returned by your endpoint for that transaction — enabling fully dynamic recurring billing without manual file uploads each cycle.
Why does Account Billing use a fixed calendar date instead of a relative interval?
Calendar-based billing is designed for batch-oriented operations where a merchant needs all charges for a given cycle to run on the same date — making reconciliation, reporting, and retry management predictable and operationally simple. It is particularly suited for businesses like insurance, utilities, and gym memberships where billing runs on a company-defined schedule rather than each customer's individual registration anniversary.
For billing that follows each customer's own start date (interval-based), use Subscription and Billing instead.
What happens to a customer who registers on the 18th when the billing date is the 5th?
On registration (18th), a void charge is executed purely to validate the card — no money is collected. The first real charge happens on the 5th of the following month at the full billing amount. There is no proration for the days between registration and the first billing date.
Can I configure retry dates if a charge fails on the primary billing date?
Yes. You can assign multiple consecutive billing dates to a single customer (e.g., the 5th, 6th, and 7th). If the charge fails on the 5th, the system automatically retries on the 6th, and again on the 7th if needed. If Send One Bill/Month is enabled, once a retry succeeds, all remaining dates for that month are skipped automatically to prevent double-charging.
Can different customers have different billing dates?
Yes. Each customer can be assigned their own billing date independently. There is no restriction to a single billing date per merchant account — you can have some customers on the 5th, others on the 15th, and others on the 20th simultaneously.
Does Account Billing support proration for customers who join mid-cycle?
No. Account Billing does not currently support proration. The first charge on the billing date is always the full billing amount, regardless of when the customer registered. If your business requires prorated charges for new customers, this calculation must be handled in your own system before registering the customer into Account Billing.
Last updated
Was this helpful?