Where to goQuickBooks Accounting Automation → Settings
Before you startConfirm the intended tenant, remote account or invoice context, and your Settings access. Keep credentials and tokens out of screenshots, tickets and exported evidence. If a previous write may have reached an external service, verify remote state before retrying.
What you’ll accomplish
Detailed client guidance covering configure default posting mappings in QuickBooks Settings, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped QuickBooks connector. This article is intentionally scoped to the behaviour enforced or exposed by the supplied module and does not treat provider marketing features as implemented integration capabilities.
How the workflow fits together
The connector keeps native CRM records authoritative while mapping verified Customer, Invoice and Payment evidence in QuickBooks. Queue, exception, API, reconciliation and compliance records are separate evidence layers, so each material action should be verified at both the native and remote sides.
Follow these steps
Open QuickBooks Accounting Automation → Settings.
Confirm you are in the intended tenant and connected company and that your role has the required Settings access.
Review current settings before editing and capture the intended change.
Change only the control required for the operational outcome.
Respect documented bounds for queues, thresholds, file limits, retention and row limits.
Save once, then verify the stored value and run a controlled test of the affected workflow.
Fields and decisions to review
This guide’s focusDetailed client guidance covering configure default posting mappings in QuickBooks Settings, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped QuickBooks connector.
Core switchesAutomatic client, invoice and payment sync, immediate processing and invoice updates can be controlled independently.
Queue limitsBatch size, retry attempts, reference refresh and health-alert intervals are bounded operational controls, not performance guarantees.
ReconciliationRemote verification is mandatory; native-payment creation, completion email, initiating-user inclusion, evidence PDF and retention are configurable.
ImportsFile count, file size, confidence, auto-create, summary-line fallback and optional extractor settings control Document Intake risk.
Logging/reportsAPI logging, payload logging and report row limits are separately configurable.
Change disciplineChange one operational control deliberately, verify the resulting behaviour and keep evidence of any production-impacting change.
Current PDF setting boundaryThe package contains A4/Letter portrait/landscape reconciliation and report PDF options consumed by its PDF generators; the current Settings save controller does not expose those option keys for editing.
API minorversionThe optional minorversion accepts a positive numeric value; leave it blank to use Intuit’s default. Switching Production/Sandbox should be treated as a reconnect event.
How to confirm it worked
Reopen the native record and the relevant integration history/register. Confirm the stored remote accounting identifier, exact amount/status, latest timestamps and the expected audit or reconciliation evidence. If the provider-side state cannot be independently verified, keep the task unresolved and use the controlled exception or troubleshooting flow.
Questions clients commonly ask
What should I verify before I trust the result?Verify the native record, the mapped remote record, the stored remote identifier, the current status/amount and the audit or history evidence. A success message alone is not the accounting evidence.
Should I press the action again after a timeout?Not until you have checked the remote accounting service and the Exceptions/API evidence. A timeout can occur after the remote side accepted a non-idempotent write, so a blind retry can create a duplicate.
Does the connector replace the native CRM record?No. Native clients, invoices and payments remain the operational source records. The connector records mappings, remote evidence and controlled reconciliation around them.
What should I include in a support case?Include the native record ID, remote ID if known, date/time, action, exact visible error and request/audit identifier. Never send client secrets, access tokens, refresh tokens or authorization headers.
Technical basis for this guidance
This guide was checked against the supplied module code paths: controllers/Quickbooks_accounting_automation.php; models/Quickbooks_accounting_automation_model.php; libraries/Quickbooks_api_client.php; libraries/Quickbooks_reconciliation_service.php; libraries/Quickbooks_document_import_service.php; views/admin; install.php; docs/FEATURE_MATRIX.md. It documents shipped behaviour, validation, routes and evidence controls; it does not claim successful live provider network calls from offline inspection.
Controls, checks and common mistakes
Work in the intended tenant and remote accounting/business context.
Do not paste credentials, access tokens, refresh tokens or private keys into tickets or notes.
Do not bypass a missing mapping, validation error, permission gate, duplicate check or remote-verification requirement.
Do not repeat a non-idempotent write until you know whether the previous request reached the remote service.
Keep native record, remote evidence and audit/history state aligned before closing the task.
Provider and accounting boundaryThe integration fails closed when required mapping, remote identity, validation, concurrency or verification evidence is missing. Do not bypass a blocker by editing unrelated records or repeating an uncertain write.
