Logging in with credentials on every request
How you'll know: It works, but each call carries a password and runs slower than it should.
Fix: Sage advises against login authentication for every request. Open one session with getAPISession and reuse the session ID until it times out; each response tells you when that will be.
Pulling the whole ledger in one query
How you'll know: Big reads time out, or return a fraction of what you expected.
Fix: Keep each query under 1,000 records and page through the rest. Very large requests can run into a 15-minute timeout, so split them by date or entity.
Writing hundreds of records in one request
How you'll know: A batch import half-fails and you can't tell which lines posted.
Fix: Keep each write under 100 records and log the result of every function in the response, so a failure points at one record, not a whole file.
Firing calls in parallel to go faster
How you'll know: Requests sit in a queue and response times climb.
Fix: Intacct caps concurrent connections per company ID and holds the rest. Throughput depends on your level of service, so a busy integration may need that conversation with your account manager, not more threads.
Entries posted without their dimensions
How you'll know: The API accepted every invoice, but the department and location reports are empty.
Fix: Unless the company makes them required, Intacct accepts many records without entity, department, class or location. Set them from the source data on every write, and reject records that can't be mapped rather than posting them untagged.