Taxes

This standard governs tax configuration and tax evidence in the accounting system of All About Pawz, LLC. The configuration: codes, rates, jurisdictions, and rules: determines what the system calculates on every sale and purchase. The evidence: what was collected, what was paid, and what was filed: is what the Company shows an examiner. Configuration set correctly once lets the evidence accumulate correctly on its own; configuration set wrong means every transaction in the period needs re-examination. The Accounting Operator maintains the day-to-day tax records and reconciles before filing; the Accounting Manager owns the configuration, the filing calendar, and every filing. The Company's tax position is governed by the Marketplace Facilitator Tax Policy and the tax documents in Regulatory of this library; this standard states the accounting procedure under them and is not tax advice. No rate is stated in this standard: rates come from the configuration and from the tax computation service, never from this document.

How sales tax works online: the tax computation service

Online sales tax is computed by the processor's tax service, not by the Platform's own tables. The service is active on the account, the head office is registered in Bartlett, Tennessee, and the account default is tax-inclusive pricing: the price the customer sees is the final price, with sales tax inside it. Every checkout line declares tax-inclusive treatment, and the checkout session enables automatic tax calculation, so the service computes the included tax from the billing or shipping address the customer provides.

Two operational consequences follow

1. The price never changes at checkout because of tax. A product priced at a given amount is that amount at the register and online; the service determines how much of that amount is tax. Where a customer asks how much tax they paid, the answer is inside the price, and the sale's tax record shows the division.
2. A tax-service failure never blocks a sale. If the tax calculation fails, checkout retries without the tax parameters. The fallback is deliberate. A sale completed during a tax-service outage may carry no calculated tax; those sales require review, because the tax obligation did not disappear with the error.

The payment notice then posts the books entry from the computed totals: checking debited for the full amount, revenue credited net of tax, and sales tax payable credited for the tax portion: only where tax was actually collected. A zero-tax sale posts no tax line; that is correct behaviour, not a missing posting. It also means the tax-payable balance reflects only what the service computed. Where the service computed nothing because it had failed, the payable is understated and the obligation still exists.

Per-sale tax records: the code, jurisdiction, rate, taxable amount, and tax amount calculated on each sale line: are written by the register for counter sales. Where a customer questions the tax on a receipt, those records are the answer: which code applied, at what rate, on what amount. See Register.

The Platform's tax configuration

The Platform's own tax configuration covers everything the tax computation service does not: counter sales, invoices, and purchases.

1. Tax codes define each tax the business handles: the code, the jurisdiction, the type, the rate, whether it compounds, the effective dates, and the payable and receivable accounts. The effective dates matter: a rate change mid-year means transactions before and after the change calculate differently, and the date range makes that happen correctly.
2. When a jurisdiction changes a rate, the operator updates the effective dates; the rate is never edited in place, or history is recalculated.
3. Jurisdictions define where: country, state, locality, and the business's registration number in each. A jurisdiction record is required everywhere the business has nexus: everywhere it must collect, file, or remit. Nexus is a legal determination, not an accounting one; the accounting system's duty is to reflect the jurisdictions the business has determined it operates in, accurately and completely.
4. Calculation rules drive automatic computation per jurisdiction and tax type.

The Accounting Manager reviews the configuration quarterly at minimum, and immediately when the Company begins selling into a new state or a jurisdiction changes its rates.

Marketplace facilitator position

For marketplace sales, the Company collects and remits sales tax as the marketplace facilitator where the law requires it, under the Marketplace Facilitator Tax Policy and the tax documents in Regulatory: the checkout calculates it, the sale records it, and the remittance procedure pays it. The operator's duty is not to decide the tax law; it is to make sure the configuration reflects the current rules, the calculations ran on every taxable sale, and the collected amounts reconcile to what was remitted. A growing gap between tax collected and tax remitted is either a timing difference: normal, where it clears monthly: or a configuration error, which is not normal and is investigated immediately.

Filing discipline

Tax filings are the output: what the business reported to each authority, when, and the confirmation. Payroll tax forms: W-2s, 1099s: are governed by Payroll; this standard covers the business's own filings: sales tax returns, business tax filings, and information returns.

1. Reconcile before filing, every time. The return's figures shall agree with the tax collected in the system for the period. Where the return and the system differ by any amount, the operator finds the cause before filing: a transaction in the wrong period, or a rounding difference that must be understood. Filing with an unexplained difference is how notices begin.
2. The reconciliation has three parts: the tax service's computed totals, the Platform's sales-tax-payable balance, and the return. All three shall agree; where they do not, the disagreement is the work.
3. File by each jurisdiction's deadline: the deadlines do not align, and each is calendared separately: and keep the confirmation and the filed return together with the underlying detail. A filed return without supporting detail is a claim the Company cannot defend.

Failure modes

1. Tax collected but never remitted. The payable balance grows month after month. The cause is procedural, not technical: nobody ran the remittance. The filing calendar control above prevents it.
2. A sale with no tax where tax was due. Check whether the tax service failed at checkout: the retry-without-tax fallback: or whether the jurisdiction configuration is missing. The journal faithfully records what the sale computed; a missing tax line means the computation produced zero, and the fix is in the configuration, not in the books.
3. Customer charged tax in a no-tax jurisdiction. The automatic calculation used the wrong address: usually a billing address applied by default where the shipping address was not collected. Refund the tax portion under the Returns and Refunds Policy and correct the address capture; do not adjust it with a journal entry and call it done.
4. Rate change applied retroactively. Someone edited the rate in place instead of dating the change, and every historical transaction now computes differently. Restore the old rate with its original dates, add the new rate with the change date, and re-examine any filings prepared in between.

Controls

• Tax records: configuration, per-sale tax records, reconciliations, filed returns, and confirmations: are kept under the Marketplace Facilitator Tax Policy, the tax documents in Regulatory, and the Regulatory Record Retention Policy.
• No rate, threshold, or figure is taken from this standard or from memory; every figure comes from the configuration in force for the transaction's date or from the tax service's computation for that sale.
• Separation of duties: the person who prepares a return does not approve its filing, and the person who records a tax payment does not reconcile the tax-payable account.
• A closed period's tax figures are never altered. A correction is made by an amended filing where the jurisdiction requires one and by a correcting entry in the open period, under Books.

Records created and where they are kept

Tax codes, jurisdictions, and calculation rules; per-sale tax records; reconciliations; filed returns and their confirmations; and remittance records are kept in the accounting system and retained under the Regulatory Record Retention Policy.

Escalation

A nexus question, a notice from a tax authority, an examination, or any legal process touching tax goes to legal@aapawz.com on the day it is received. Configuration and computation failures go to the Accounting Manager and, where the cause is a system failure, to support@aapawz.com.

Review cadence

The Accounting Manager reviews the tax configuration quarterly, reconciles before every filing, and reviews the filing calendar monthly. This standard is reviewed whenever the Marketplace Facilitator Tax Policy or a Regulatory tax document changes.