How to Automate Bsale

A sale in Bsale is a tax document before it is anything else

Bsale is a sales and business management system for small and medium businesses in Chile, Mexico and Peru, each version built to that country's tax rules. Its customers are retail shops, fashion, food and drink, and businesses selling over a counter and online at once.

What sits at the centre is not the till, it is the document. In Chile, Bsale is authorised by the SII to issue electronic tax documents, so ringing up a sale produces a boleta or factura with a folio number the tax authority also knows about. The same system issues notas de credito and notas de debito, guias de despacho and facturas de compra. In Peru the equivalent job answers to SUNAT.

So the sales ledger and the tax record are one object rather than two. That is a relief for a small business, and it means every correction is itself a document, visible to somebody outside the shop.

The month closes on documents that arrive from elsewhere

Issuing is the solved half. Everything that arrives is the other one.

A supplier's documents get registered against the business whether or not anybody has seen them, so the purchases side of the month comes off a portal, not out of a drawer. What the shop issued has to agree with what is registered under its name, and a document that was rejected, or went out against the wrong RUT, is a problem only once somebody finds it.

Around that sits the ordinary week. Card settlements have to be matched to the day's boletas. The online store's stock has to be checked against the shop's, because the last one on the shelf can sell twice. Suppliers get ordered from on their own sites, credit notes get chased for returns promised across the counter, and somebody counts the cash and squares it against the caja.

All of it lands on an owner, a part-time contador, or both, in one week.

Bsale

Issued against registered This month's boletas and facturas checked off against what the tax authority holds in your name, with rejections and folio gaps named.

Purchases you never saw Supplier documents registered against the business collected and matched to goods that actually arrived, before the month is closed.

The counter and the website agree Stock in the shop checked against the online store, so the last one on the shelf is not sold twice in the same afternoon.

Bsale issues the tax document as the sale is rung up

For a business this size the system carries far more than a till, and most of it goes unopened.

The point of sale finds products with a barcode reader or by keyword and SKU, keeps favourites for whatever sells all day, applies configurable discounts and takes several payment methods. The caja records an opening balance, every deposit and withdrawal, and closes the shift with a summary. Inventory updates in real time across branches and sales channels, carries purchase price and rotation beside each quantity, and can be counted from the mobile app. Reports run by sale, document, discount, stock movement, price and customer, and export to Excel. Quotations carry an expiry date and take advance payments. User permissions are how unauthorised discounts get closed off, and the ecommerce side sells from the same catalogue as the counter.

Every one of those is a record of documents Bsale itself issued.

The supplier's ordering site is not. Neither is the bank, the marketplace, the courier's tracking page, or the tax authority's record of what was registered in your name. Each is a login holding half of a comparison the business must make anyway.

A shop can reconcile itself against the tax authority

Every document Bsale issued has a folio number, and that number exists in a second place. Comparing the two lists is the job.

What the shop issued this month, set against what is registered under its name, so a rejected document or a hole in a folio range turns up in the first week, not at the deadline. Supplier documents registered against the shop, matched to what arrived, so a factura nobody remembers is a question while the goods can be traced.

Credit notes tracked against the returns that caused them, so the customer who was promised one and never got it stops being a complaint. Card settlements laid against the day's boletas, so a deposit that came up short is named on Tuesday.

Then the ordinary retail work. Supplier prices read off their own sites and compared with the purchase price on each product, so a thinning margin shows up before the season's order goes in. The online store's stock checked against the shop's, so the jacket that sold at midday is not still listed at four.

The reading runs overnight with nobody watching, because reading changes nothing. Anything that alters a document, goes to the tax authority or reaches a customer is drafted and waits for the owner or the contador.

Reading the SII portal is nobody's idea of a job

That comparison still needs a person to open two systems and read them line by line, and that person is running the shop.

WebRun is an AI agent that runs a real Chrome browser, signed in as you. It opens the tax authority's portal, the bank, a supplier's site or the marketplace, reads the screen, and sets it beside what Bsale recorded, with the differences named.

Runs happen on a schedule you set, in your own private environment, and you can watch one and stop it. Nothing is submitted, corrected or sent until a person has approved it.

The workflows below are already built, and each one says what it compares.