Automation pays off in a specific order, and getting that order wrong is how people end up with an expensive system nobody uses. For account payable software, here is what to automate first, what to leave alone, and where this product fits.
What is worth automating, in order
There is a sequence here and it is worth following, because each step removes more work than the one after it.
First, stop retyping. Customers and items stored once, with their GSTIN, state, HSN and rate, so the fortieth invoice costs no more effort than the first and the details are right on all of them. This is the single biggest saving and it is not really automation, just records. Second, the recurring invoices — the rents, retainers, subscriptions and maintenance contracts that are the same every month. Third, the reminders, because chasing is the task nobody does on schedule. Fourth, the return figures, exported rather than compiled.
What comes after that is the interesting part, and it is where most automation projects go wrong: reading documents that arrive from elsewhere. That is genuinely harder, genuinely useful, and should never be trusted without a person approving the result.
Accounts payable: the other direction entirely
Everything else on this page is about invoices you issue. Accounts payable is about invoices that arrive, and it is a different problem with a different kind of software.
The full version of AP automation is a workflow: the supplier invoice is captured, the data extracted, matched against the purchase order and the goods receipt, routed to whoever is authorised to approve that amount, posted, scheduled for payment, and paid in a batch. In a large business that is dozens of people and thousands of documents, and products exist specifically for it.
In India there is a layer on top that no generic AP product handles well: input tax credit does not depend on holding the supplier's invoice, it depends on the supplier having actually declared it. So the matching that matters is not only against your purchase order — it is against GSTR-2B. A supplier who has not filed leaves you holding a bill and no credit, and the only way to know is to reconcile.
To be clear about this product: it does GST purchase recording and 2A/2B reconciliation, which is the India-specific half, and the AI bill scanning reads a supplier invoice into a record for a person to check. It is not an AP workflow suite — no approval hierarchies, no three-way match, no payment runs. Below roughly a hundred supplier bills a month that is usually fine. Well above it, buy something built for it.
What runs by itself here
- Recurring invoices on the cycle you set, numbered in your ordinary series.
- Payment reminders sent on a schedule rather than when someone remembers.
- Customers and items stored once — the largest saving, and the least glamorous.
- Tax derived rather than typed, per line, from the item rate and the place of supply.
- A receivables position, aged, without adding anything up.
- AI bill scanning that reads a supplier invoice into a record for a person to confirm.
- GSTR-1 and GSTR-3B figures exported rather than compiled by hand.
- Full export to CSV, Excel and JSON, on every plan including the free one.
- Free to start — ₹0, no card, no expiry.
Automating a recurring invoice safely
- Start free now, and enter your business details and GSTIN once.
- Add the customer properly — GSTIN, address and state — because the place of supply is derived from it and will be repeated every month.
- Add the item or service with its HSN or SAC code and the correct rate. This is the field that must be right before anything runs on a schedule.
- Create the recurring invoice with its cycle and, if the contract has one, its end date.
- Let the first one run, then open it and read it properly — period, rate, place of supply, tax split, numbering.
- Switch on reminders once you are satisfied the invoice itself is right.
- Review your list of active schedules once a quarter, and stop the ones whose contracts have ended.
What should stay manual
Worth naming, because the instinct with automation is to keep going until everything is automated, and some things get worse that way.
Anything with a judgement in it. A rate on an unusual supply, the place of supply on a service that could be read two ways, whether a discount reduces the taxable value or sits outside it. Automating a judgement means making it once and then repeating it without noticing, and these are the judgements that attract questions.
The first invoice of any new recurring series, as above. And any credit note, because a credit note is always a correction of something and corrections should be looked at by a person who knows why.
Also: approvals. If somebody has to agree to an amount, having software route it to them is useful, but having software agree on their behalf because it is usually fine is how a business discovers it has been paying for something nobody wanted for two years.
The good rule is that automation should remove typing, not decisions. Where it starts removing decisions, slow down.
The reconciliation that actually has to be automated
Of all the repetitive work in Indian billing, the one with the worst ratio of effort to judgement is matching your purchase register against GSTR-2B. It is hundreds of comparisons a month, every one of them mechanical, and the consequence of skipping it is a credit claimed that is not available.
The reason it cannot be done by eye is the near-misses. An invoice number typed with a different prefix, a date a day out, a figure differing by a rupee of rounding, a supplier who filed in the following period. Each of those is a match a person would make and a naive comparison would not, and each of the real mismatches looks the same as the trivial ones until it is examined.
So the useful output is not a tick list but a sorted one: matched, matched with a small difference, in your books but not in 2B, in 2B but not in your books. Only the third category needs chasing, and it is usually a fraction of the total.
This is the part worth having software for even if you automate nothing else, because it is the one where doing it by hand means not doing it.
HSN and SAC codes, and how many digits you need
Every line on a tax invoice needs an HSN code for goods or a SAC for services. How many digits depends on your aggregate turnover in the preceding financial year — smaller businesses report fewer digits than larger ones, and B2B and B2C invoices are treated differently.
Because the requirement is tied to turnover and has been tightened in stages, the practical answer is to store the fullest code you can against each product once, and let the software report at the level required. A six-digit code can always be truncated; a two-digit one cannot be expanded.
Billixo keeps the code on the product record and carries it onto every line automatically, and its AI HSN lookup will suggest one from a plain description when you genuinely do not know.
Invoice numbering: one unbroken series per year
The invoice number has to be consecutive, unique within the financial year, and no more than sixteen characters of letters, numbers, slashes and hyphens. Gaps invite questions. Duplicates cause them.
This is the single most common reason a spreadsheet-based billing setup fails an audit: two people billing on two machines, both starting from the last number they remember. A system that issues the number centrally cannot make that mistake.
The series restarts on 1 April, and Billixo restarts it for you rather than waiting to be told.
The AI, and what it is actually for
The useful application of AI to billing is not a chatbot. It is the twenty minutes a day spent retyping things that already exist on paper.
- Scan a supplier bill. Photograph it; the lines, the GSTIN, the tax and the totals come back as a draft you check rather than a form you fill.
- Find the HSN code. Describe the product in plain words and get a code to confirm, instead of scrolling a list of eleven thousand.
- Ask about your own numbers. "What is outstanding over sixty days?" answered from your data, not a manual.
- Write the reminder. A polite, specific chase for an overdue invoice, ready to send on WhatsApp.
Nothing is sent anywhere until you ask for it, and the platform runs on whichever model it has been configured with — including one hosted on your own server.
Who this actually suits
It fits a business that raises between a handful and a few hundred invoices a month and would rather not think about GST between the 10th and the 20th: traders, distributors, retail counters, workshops, agencies, consultants, contractors and manufacturers who sell on invoice.
It fits less well if you need deep manufacturing costing, multi-currency consolidation, or payroll — those are different products, and pretending otherwise wastes your evaluation time.
If you are not sure which side of that line you fall on, the free plan answers it in an afternoon at no cost. Start free now.
Free, and what it costs you instead
Free software usually costs you something that is not money: your data held hostage, an export that does not work, ads inside your invoice, or a "free" tier so narrow it is a demo with a login screen.
The line here is drawn differently. Export works on the free plan — CSV, Excel and JSON — because data you cannot get out is not data you own. The invoice is a real compliant invoice, not a sample. The limits are on volume and on the conveniences, not on whether the thing works.
Start free now. If it does not suit you, take your data with you.
Where your data lives
On the server this platform is installed on. Every record carries a company identifier and every query is scoped to the signed-in account at the framework level, so one business cannot read another’s data by any route, including a crafted one.
Sign-in is rate limited, sessions can be restricted to one device per user, and passwords are stored hashed. Exports are available on every plan, free included: if you ever want to leave, your data leaves with you.
Frequently asked questions
Is any of this on the free plan?
The free plan does the part that saves the most time: customers and items stored once, so invoices are assembled rather than typed. Recurring invoices, reminders and the GSTR exports are on the paid plans, and every new account gets the full set for its first fortnight.
Can it raise the same invoice every month automatically?
Yes — recurring invoices on the cycle you set, numbered in your ordinary consecutive series so they sit correctly alongside manual ones. Check the first one it produces properly, because after that nobody reads them, which is both the point and the risk.
Does it chase customers for payment?
It sends payment reminders on a schedule on the paid plans. That removes the part people actually fail at, which is sending them consistently rather than writing them.
Are the invoices valid for GST?
Yes. Every invoice carries the fields Rule 46 requires — GSTIN, HSN/SAC on each line, place of supply, the correct CGST/SGST or IGST split, and a consecutive invoice series that restarts each financial year.
Can I move my existing customers and products in?
Yes. Bulk import from CSV or Excel on any paid plan, and export back out in CSV, Excel or JSON at any time, including on Free. Most people bring their party and item lists across in one pass and carry outstanding invoices as opening balances.
Start free, decide later
You do not have to choose a plan to begin. Start on Free, use it for as long as it suits you, and upgrade only when a limit actually gets in your way — never automatically, and never because a countdown ran out.
Open the software demo → — or create the free account from the same page.
Read the full details → on the home page, including pricing and the AI features.
Related pages