Counter billing or POS
Records an immediate sale and often connects item selection, price, tax, payment, receipt, stock and shift close. Hardware and outage behavior may be part of the decision.
Billing software evaluation
Billing software: choose the record before the feature
A fast bill is useful only when the business can explain it later. Test what was sold, price and tax, payment status, stock movement, corrections, closing totals and recovery before choosing a product from its feature list.
Evidence and review scope
Evidence reviewed 2026-08-18. This review uses Posnic v1.3.0 at exact source commit b531ef4308c4dc3a25f250551a54fc5616e3b8d9, one reproduced local Windows sale, one synthetic backup and restore, 37 rerun receipt and report source tests, product documentation and primary invoice, barcode, payment and security sources.
Stable release: v1.3.0. No complete counter shift, physical receipt print, barcode scan, processor settlement, tax acceptance, customer migration or production cutover was executed.
Billing, invoicing, accounting and ERP are not automatic synonyms
Search results often mix these categories. Start with the record and operating decision your business needs, then verify whether one system or an accepted integration owns it.
Invoicing
Creates a request for payment, often with due date, customer identity, terms, reminders, credit notes and receivables status. It may not manage a checkout counter or perpetual stock.
Accounting
Maintains ledgers, control accounts, financial periods and statements. A POS total is an input to reconcile, not evidence that correct accounting entries were posted.
ERP
Can span purchasing, inventory, production, finance, people and other operations. Ordinary billing fields do not establish manufacturing, project, payroll or enterprise-planning workflows.
Nine records a business should be able to explain
Sale identity
Stable sale or invoice number, timestamp, branch, counter, operator and original line items.
Item and quantity
Product or service identity, description, unit, quantity and any serial, batch or variant required by the workflow.
Price and discount
List or agreed price, approved discount, promotion, override reason and the person authorized to change it.
Tax result
Taxable value, rate or category, amount, exemption or reverse-charge treatment and jurisdiction-required particulars.
Payment state
Tender, amount, change, provider reference, credit or balance due, plus uncertain and refunded states.
Correction history
Return, credit, cancellation or edit linked to the original record, reason, authorization and financial effect.
Stock movement
Receiving, sale, return, damage and adjustment connected to item, branch, quantity, user and reason.
Close and settlement
Shift totals compared with cash, payment-provider and credit evidence, with every difference assigned.
Recovery evidence
Export, backup, retention and tested restore evidence that can reproduce representative records after failure.
Billing software acceptance matrix
Prepare a small reference set with predicted results. Compare the transaction, independent payment evidence and stock record instead of trusting one screen in isolation.
| Test | Expected business result | Evidence to retain |
|---|---|---|
| Release and configuration | The exact application, tax, currency, timezone, numbering and permission setup is reproducible. | Version, source or installer hash, configuration export and approver. |
| Normal sale | Items, quantities, price, discount, tax, total and payment agree across all records. | Sale ID, receipt, transaction row, stock movement and close report. |
| Discount and override | An approved discount works and an unauthorized price change is blocked or traceable. | Role, input, calculation, reason and audit record. |
| Invoice and tax | The sample contains every current required particular and calculation for the target market. | Dated sample and named qualified tax or accounting approval. |
| Cash and change | Cash received, change, drawer expectation and close total reconcile. | Receipt, expected cash, actual cash and difference reason. |
| Electronic payment | Approved, declined, timeout, duplicate and uncertain cases have one controlled outcome. | POS record, terminal or provider reference, settlement and refund evidence. |
| Credit or amount due | Customer, due amount, payment history and later settlement stay traceable. | Customer ledger or accepted external receivable record and reconciliation. |
| Return and cancellation | The original transaction, refund, tax, stock and authorization remain linked. | Original and correcting IDs, reason, approval and resulting reports. |
| Receiving and stock | Known receiving, sale, return and adjustment quantities reconcile for one item. | Purchase reference, movement history, count and variance explanation. |
| Day close and export | Filters, timezone, branch, staff and tender totals match the reference set and exported rows. | Close report, export hash, row count and independent recomputation. |
| Outage path | Each local, network, payment, printer and cloud dependency behaves according to a written fallback. | Timed drill, unavailable functions, queued work and recovery result. |
| Backup and restore | A separate backup restores representative items, sales, settings and reports to the expected state. | Backup hash, storage location, restore log, counts, elapsed time and approval. |
What Posnic v1.3.0 evidence establishes
One local sale was reproduced
A disposable Windows profile completed and reopened synthetic sale S-O2MA-000001 for INR 125 in cash while external hosts were blocked inside Electron. This was not an operating-system-wide network disconnection or complete shift.
37 focused billing-record tests passed
Thirteen column, eight receipt, eight daily-report, five local-asset and three sales call-path checks passed at the exact pinned commit. They cover source formatting and boundaries, not a physical receipt or business acceptance.
58 mm and 80 mm text bounds were tested
The source tests check quantity and amount alignment, weighted and counted lines, long-name wrapping, optional rows, drawer and cut commands and daily-report formatting for both roll widths.
Print assets were local in the reviewed source
Five checks cover local scripts, content-security policy, the vendored print library, build copying and page references. This is source evidence, not a production security audit.
A synthetic restore was checked
The disposable profile restored 20 collections and 53 documents with matching totals. It did not test a production database, lost disk, encrypted archive, retention policy or replacement computer.
Physical hardware remains an acceptance gate
No physical receipt printer, barcode scanner, cash drawer, scale or payment terminal was connected in this billing review. Use the pinned hardware matrix and test the exact devices.
Reconcile three records, not one dashboard number
Transaction record
- Sale or invoice ID and original lines.
- Quantity, price, discount, tax and total.
- Returns, cancellations and corrections.
- Operator, branch, counter and timestamp.
Independent evidence
- Cash count and drawer expectation.
- Payment terminal, provider and settlement records.
- Physical stock count and supplier receiving.
- Bank, receivable or accounting records where applicable.
Acceptance rule: a difference is not solved by changing the report until it matches. Preserve the original result, identify the source, record the correction and keep named approval.
An eight-step billing-software pilot
Step 1
Name the record owner
Decide which system owns sale, invoice, payment, receivable, stock and accounting records.
Step 2
Map requirements
List invoice fields, numbering, tax, currencies, units, tenders, permissions and retention obligations.
Step 3
Create a reference set
Use representative items, customers, tax cases, payments, returns and stock with predicted totals.
Step 4
Run counter cases
Test normal and exception paths with the exact roles, printer, scanner and payment arrangement.
Step 5
Reconcile and export
Compare transaction, payment, stock and accounting evidence; recompute exports independently.
Step 6
Break dependencies
Run controlled network, provider, printer and cloud outages and document every fallback.
Step 7
Restore the reference set
Use separate storage, measure recovery and compare item, sale, setting and report counts.
Step 8
Approve a bounded rollout
Assign every gap, workaround and deadline, then obtain operations, finance, tax and owner approval.
Product screens worth inspecting
These are real Posnic screens shown in full. They reveal surfaces to test and do not imply that the records reconciled across a complete business day.
Invoice and tax acceptance is jurisdiction-specific
A template can look professional and still omit a required field or use the wrong tax treatment. Review current official rules for every market and sale type, then preserve dated accepted samples.
India
CBIC publishes GST invoice rules with required particulars and special cases. Determine current applicability, electronic-invoice obligations and retention with qualified advice.
United Kingdom
GOV.UK publishes general invoice particulars and separate VAT invoice requirements. A till receipt, simplified VAT invoice and full VAT invoice can have different rules.
European Union
The European Commission summarizes EU VAT invoicing rules and credit-note references. Member-state and transaction-specific requirements still need review.
Posnic does not claim GST, VAT, sales-tax, electronic-invoice or fiscal-device certification. Country support must be based on accepted output from the exact release and configuration.
Payment, barcode and security boundaries
Payment is a separate trust boundary
PCI SSC merchant resources frame payment security across people, process and technology. Confirm processor, acquirer, terminal, network, validation and incident responsibilities.
A barcode identifies; it does not clean data
GS1 documents EAN/UPC use at retail POS. The shop must still verify item mapping, unit, price, duplicate handling, label quality and the exact scanner.
Recovery needs more than a backup button
CISA small-business resources cover practical cyber and resilience controls. Keep separate copies, access control, retention, tested restore and an incident owner.
Run the 24-record billing software checklist
The worksheet covers release, record ownership, item data, invoices, tax, cash, electronic payment, credit, return, receiving, stock, close, exports, permissions, hardware, outages, backup, restore and qualified approval. Observation and decision fields are blank so the file cannot present an unexecuted trial as passed.
Primary product and standards sources
Posnic v1.3.0 release
The public stable release and package boundary used for this review.
Posnic pinned source tests
The exact receipt, report, local-asset and sales call-path files used for the 37-test rerun.
Posnic runtime method
Public evidence for the limited local sale and synthetic backup/restore observations.
CBIC GST invoice rules
Official India source for GST invoice particulars and related cases.
GOV.UK invoice requirements
Official UK guidance for invoices and the additional information required on VAT invoices.
European Commission VAT invoicing
Official EU overview for VAT invoice requirements and credit-note references.
PCI SSC merchant resources
Primary payment-security material for merchant responsibilities and PCI DSS scope.
GS1 EAN/UPC standards
Primary barcode context for retail point-of-sale identification and scanning.
CISA small-business resources
Primary US government resources for practical cybersecurity and resilience planning.
Continue with the right intent owner
Questions
What is the difference between billing software and POS software?
The terms overlap, but billing software usually emphasizes sale or invoice records. A POS may also include counter hardware, payments, stock, purchasing, staff controls and operational reports. Compare the required records and tested workflow rather than the label.
Is billing software the same as invoicing or accounting software?
Not necessarily. Invoicing can focus on amounts owed and collection; accounting maintains ledgers and financial statements; counter billing records a sale at checkout. One product may combine them, but the buyer must test the actual posting and reconciliation boundaries.
Does offline billing software mean every task works without internet?
No. A local sale may continue while card authorization, hosted ordering, remote dashboards, support, updates or cloud synchronization still need a network. Test every dependency separately.
Is Posnic certified for GST, VAT or sales-tax compliance?
No certification is claimed. Posnic contains tax and invoice fields, but each business must verify required particulars, numbering, tax treatment, electronic invoicing and retention with current rules and qualified local advice.
Does a payment marked successful in billing software prove settlement?
No. Reconcile the POS transaction with cash evidence or the payment provider and acquirer record. Test timeout, duplicate, uncertain, refund and settlement-difference cases.
Will Posnic work with any receipt printer or barcode scanner?
No universal hardware claim is made. The pinned release has source and protocol evidence with stated limitations, but no physical printer or scanner was connected in this billing review. Test the exact make, model, connection and workflow.
What should a shop test before using billing software live?
Run representative sales, discounts, tax, cash and electronic payments, credit, returns, receiving, stock, day close, reports, permissions, outages, backup and restore on the exact release, computer and hardware planned for the counter.
Where Posnic fits today
Posnic Community Edition v1.3.0 has one reproduced local Windows sale, one synthetic backup and restore, 37 focused receipt and report tests, and inspectable source. It does not have accepted evidence for a complete counter shift, physical receipt, physical scanner, processor settlement, tax certification, customer migration or production cutover. Use the worksheet to decide whether the current release fits a bounded pilot.