ImmiAccount for Migration Agents: Organisation Accounts, Team Access and a Cleaner Lodgment Workflow (2026)

Every application your practice prepares ends its journey in the same place: ImmiAccount. It is the single most used piece of government infrastructure in your working week — and most practices run it on habits formed when the practice was one person. This guide covers how to structure accounts and access for a team, the attachment and payment details that cause avoidable friction, and how to build a lodgment workflow around ImmiAccount that scales past a single agent.

Individual vs organisation accounts: get the structure right first

ImmiAccount offers individual and organisation account types. A practice with staff should be running an organisation account: it puts the firm's lodgments under one umbrella, gives an account administrator control over who has access, and means applications do not live and die with one person's login.

The non-negotiable that follows: every staff member gets their own login, and nobody shares credentials. Shared logins fail on three fronts at once — security (one phished password exposes everything), accountability (no audit trail of who did what), and offboarding (a departing staff member walks out knowing the password to your entire lodgment history). When someone leaves, their access is removed the same day, not at the next quarterly clean-up.

Lock it down

• Multi-factor authentication on every account. ImmiAccount supports MFA and your practice should treat it as mandatory, not optional — an authenticator app, not SMS where you can avoid it.
• Unique, managed passwords. Store them in a proper password manager at the practice level, never in a spreadsheet or a drawer.
• Review access quarterly. The account administrator confirms the user list still matches the staff list. It takes five minutes and catches the offboarding that got missed.

Attachment discipline: where hours go to die

Uploading evidence is the least glamorous and most time-consuming part of lodgment. Three habits recover most of the lost time:

• Respect the limits before you reach them. ImmiAccount imposes per-file size limits (commonly 5MB) and a capped number of attachment slots per applicant (commonly 60) — the current limits are displayed in the attachment screens. Plan the evidence bundle against those constraints before upload day, not during it.
• Bundle logically, name descriptively. One merged, bookmarked PDF per evidence category beats forty loose photos. Match each upload to the correct document type in the dropdown and give it a filename a case officer can trust at a glance.
• Compress and convert before you upload. Phone photos and scans routinely blow the size limit. Batch-convert to PDF and compress as part of document preparation — our document checklist guide covers what to collect; the preparation step is where you make it lodgment-ready. (LodgeHQ builds this in: client uploads are converted, compressed and merged into lodgment-ready bundles automatically.)

Payments: quote the surcharge or eat the surprise

Visa application charges paid by card in ImmiAccount attract a surcharge — around 1.4% for Visa and Mastercard, higher for some other cards. On a partner visa charge of $11,710, that is real money, and a client who first hears about it at the payment screen is a client who feels ambushed. Quote the VAC, the surcharge and your professional fee as separate lines from day one — our fee benchmarks guide covers the full cost conversation. Decide up front whether the client pays in session, pre-loads funds to you (with proper clients' account handling), or pays by an alternative method with a lower surcharge.

Outages, maintenance and the deadline rule

ImmiAccount goes down — scheduled maintenance windows on weekends, and occasionally at the worst possible moment. The rule that removes the risk: never plan to lodge a deadline-critical application on its last possible day. A review application due day 21 gets lodged by day 14; a bridging-visa-sensitive lodgment happens the week before the substantive visa ceases, not the night it ceases. If an outage does bite on a critical date, document everything — screenshots with timestamps, error messages, the works — contemporaneous evidence is what makes any later argument possible. Our ART deadlines guide covers why late simply is not an option.

Prefill tools: the compliant way to stop re-typing

The forms inside ImmiAccount are long, repetitive and unforgiving — the same passport number, address history and family composition typed again and again across applications. Tools now exist (LodgeHQ's eLodge browser extension among them) that prefill ImmiAccount forms from the verified data already sitting in your case management system. Used properly, they remove transcription errors and hours of re-keying. "Properly" means three things:

1. The source data is verified first — prefill from client questionnaire answers and documents you have checked, not from unreviewed intake data.
2. The agent reviews every field before moving on. Prefill is a typing assistant, not a decision-maker. You remain responsible for every answer on the form, and providing incorrect information carries serious consequences under the Migration Act for your client and for you.
3. A human lodges. Review the summary, make the declarations and submit personally. Automation that lodges applications by itself is a line no compliant practice should cross.

The workflow around the portal

ImmiAccount is the last step of a pipeline, and the pipeline determines whether lodgment day is calm or chaotic. The shape that works:

1. Intake and conflict check, then a signed agreement before substantive work — see the Code compliance checklist;
2. Structured questionnaire to the client, so data arrives once, in the shape the forms need;
3. Document checklist tracked to completion, with client uploads converted and bundled as they arrive;
4. Prefill, review, lodge — with the agent checking every field;
5. Capture the artefacts immediately: TRN recorded on the matter, lodgment receipt and submitted-form PDF filed, VAC receipt to the client, next deadline diarised;
6. Track processing against published times — our processing times guide covers managing the wait.

Run that pipeline matter after matter and lodgment stops being an event — it becomes the boring, reliable end of a process that started weeks earlier.

LodgeHQ is built to be the system on the other side of ImmiAccount: questionnaires that collect the data once, document checklists with automatic conversion and bundling, eLodge prefill with the agent in control of every field, and TRN, receipts and deadlines captured on the matter. Start a free 14-day trial and make lodgment day the easiest day of the file.