End of employment in Maryland: a complete employer guide (2026)
Maryland gives employers flexibility when ending employment, but mistakes at this stage can be costly.
Most roles follow at-will employment, which means either the employer or the employee can end the relationship without needing to give a reason in many cases.
Even so, that default rule is only the starting point. Employers still need to navigate Maryland’s termination laws, wage payment obligations, discrimination and retaliation risk, mass layoff notice duties (including federal WARN Act considerations where applicable), and the enforceability of post-employment restrictions such as non-compete and non-solicitation clauses (subject to Maryland-specific limitations).
For HR leaders and international employers, the real challenge is not simply ending the employment relationship. It is managing the notice period in Maryland, final wages, severance arrangements, benefits continuation, and exit documentation in a way that stands up if challenged later by regulators or through litigation.
This guide explains the practical rules that govern the end of a contract in Maryland and broader employee exits, with a focus on the 2026 compliance landscape and the operational risks employers need to control.
1. At-will termination in Maryland, the default rule
At-will termination in Maryland is the default rule, which means either side can usually end the employment relationship at any time, with or without cause, unless a contract, statute, or clear public policy says otherwise.
That baseline shapes most termination of employment in Maryland, but it does not give employers unlimited freedom. The real risk sits in the exceptions. Maryland Department of Labor and the Maryland General Assembly both frame Maryland employment law around that practical distinction.
For employers, Maryland’s termination laws are therefore less about whether employment is generally at will and more about whether a dismissal crosses into discrimination, retaliation, breach of contract, or wage-payment violations. That is why documentation, consistent reasoning, and disciplined offboarding matter far more than the label used in the HR file.
What at-will means for Maryland employers?
At-will means an employer can dismiss an employee without proving cause, and the employee can resign without serving notice, unless a written agreement changes that position. A fixed-term contract, a just-cause clause, or a severance promise can all narrow that flexibility.
In practice, that means termination without cause in Maryland is usually lawful, but only if the real reason is not discriminatory, retaliatory, or otherwise unlawful. It also means termination for cause in Maryland should not be treated casually. If the employer says dismissal was for misconduct, the file should support that claim with warnings, policy references, witness accounts, or investigation notes.
Exceptions to at-will, statutory and common law in Maryland
The key exceptions are statutory rights, public policy, and contract. Statutory claims can arise if a dismissal is tied to protected characteristics, protected complaints, leave use, or wage claims under laws such as anti-discrimination statutes or wage protection laws. Public policy claims can arise where an employee is dismissed for doing something the law protects, such as refusing illegal conduct or asserting a legal right. Contract claims can arise where handbook language or offer terms limit dismissal to cause.
That is where wrongful termination in Maryland usually starts. Employers often assume the at-will label ends the analysis, when it only starts it. A well-drafted handbook disclaimer still matters because loose wording around “permanent employment” or discipline steps can weaken the employer’s position later.
Termination for cause vs termination without cause in Maryland
Termination for cause in Maryland usually points to misconduct, serious policy breaches, dishonesty, violence, or repeated performance failures after clear warnings.
On the other hand, Termination without cause in Maryland usually describes restructuring, redundancy, budget cuts, or role elimination without employee fault.
That difference can influence unemployment outcomes, severance drafting, and claim risk. Maryland unemployment guidance states that misconduct findings can delay or disqualify benefits, which means a “for cause” label should only be used where the evidence supports it.
2. Notice periods in Maryland
There is no statutory notice period in Maryland for an individual dismissal, but notice still matters in contracts, layoffs, and risk management.
Maryland law does not require advance notice before ending one employee’s job in the ordinary course. The bigger question is when notice becomes commercially sensible, contractually binding, or required under layoff rules.
That is why the absence of a statutory individual notice rule does not make notice irrelevant in practice. A rushed dismissal can increase the appearance of unfairness, create confusion over property return and access controls, and make later defence harder if the employee alleges wrongful termination in Maryland or related claims.
Is advance notice required?
For individual dismissals, there’s no law in Maryland that requires advance notice. Immediate dismissal is usually permitted in an at-will setting. But large-scale reductions are different. Federal WARN can require 60 days’ notice, and Maryland’s Economic Stabilization Act now imposes its own 60-day state notice regime for certain reductions in operations where statutory thresholds are met.
So, although many people still search for the notice period in Maryland as if there were one universal rule, the correct answer is split. Individual terminations usually require no statutory notice. Contract exits, federal WARN events, and Maryland ESA events can require notice or a careful substitute such as pay in lieu, depending on the facts.
Contractual notice periods in Maryland
Where a contract states a notice period, that term is binding. Ignoring it can turn an otherwise lawful exit into a breach of contract claim. If the employer wants the employee to leave immediately, the usual commercial solution is salary or benefits in lieu of notice.
That point is especially important at the end of a contract in Maryland where the agreement contains renewal, early-exit, or notice language. For senior roles, project roles, and federal-contractor roles, the practical Maryland employee termination process should start with the contract before it starts with policy.
Notice best practices for Maryland employers
Best practice is to use written notice even where the law does not force it to support documentation and reduce legal risk. For non-cause exits, two weeks’ written notice or pay in lieu is often more defensible than same-day dismissal. A termination letter should confirm the effective date, the reason stated at a high level, return-of-property steps, and the final pay date.
A disciplined Maryland employee termination process also means revoking access at the right moment, having HR present, and ensuring the manager’s spoken explanation matches the written record to avoid inconsistencies that may be challenged later. Those operational details often decide whether a later claim looks credible.
3. Final pay rules in Maryland
In Maryland, final pay rules are strict, and mistakes here are expensive because late or incomplete payment can lead to enhanced damages and legal fees. Maryland law requires final wages to be paid by the next regular payday, not whenever the employer finishes internal paperwork or internal approval processes.
That makes final pay one of the most important compliance steps in termination of employment in Maryland. Maryland General Assembly, §3-505 and §3-507.2 set the core rules.
Employers should treat final pay as a same-day workflow trigger. Once the termination date is set, payroll, HR, finance, and the manager should already know what must be paid, what may be paid, and what may not be deducted.
When must final wages be paid?
Maryland requires all wages due for work performed before termination to be paid on or before the day the employee would have been paid if employment had continued. That means the next regular payday as defined by the employer’s established pay schedule. There is no state rule requiring payment on the day of discharge.
That rule applies to resignations and dismissals alike. If payroll misses the regular cycle, the employer is already in a dangerous place under Maryland’s final pay rules, especially if there is no genuine dispute about what was owed.
What is included in final pay?
The statute expressly includes bonuses, commissions, and fringe benefits within the wage definition, which is why disputes often center on sales incentives, earned bonuses, and leave payout.
Unused leave is not automatically payable in every case. Section 3-505 allows an employer to refuse payout of accrued leave if it has a written policy limiting payout, the employee was notified of leave benefits as required, and the employee is not entitled to payment under that written policy (provided the policy is clear, consistently applied, and compliant with Maryland law).
Deductions from final pay, what is permitted in Maryland
Maryland generally bars wage deductions unless they are court-ordered, expressly authorised in writing by the employee, allowed by the Commissioner, or otherwise authorised by law. That means employers should be very cautious about deducting for equipment loss, breakage, shortages, or similar issues after separation without proper legal basis.
In practical terms, unreturned property should usually be handled through recovery procedures, not by raiding the final payslip. That point becomes critical during the Maryland employee termination process, because an unlawful deduction can create a wage claim even where the dismissal itself was lawful.
Penalties for late final pay, treble damages in Maryland
Maryland allows a court to award up to three times the unpaid wage, plus reasonable counsel fees and costs, where wages were withheld and there was no bona fide dispute. That is the real force behind Maryland’s final pay rules.
A withheld 10,000.00 USD commission can therefore become a claim worth up to 30,000.00 USD before fees excluding additional legal costs and potential reputational impact. The lesson is simple, employers should only withhold final compensation where they can show a real, good-faith dispute, not because internal approval is late or emotions are high after the exit.
4. Severance pay in Maryland
Severance pay in Maryland is not required by statute, but it often becomes binding through contract, policy, consistent past practice, or a release agreement. That is why employers should not treat severance as a discretionary courtesy once they have created clear expectations around it. In executive exits and group reductions, a badly handled severance programme can create as much risk as the termination itself from both a contractual and discrimination perspective.
This is also where language matters. A Maryland severance agreement is not just a payment document. It is often the place where employers seek to secure a release of claims, protect confidentiality, and manage transition obligations.
Is severance pay required?
There is no general Maryland law requiring employers to offer severance in individual terminations. That means there is no automatic right to redundancy pay in Maryland merely because a job ends. If severance is owed, it is usually because a contract, policy, established practice, or release deal says so.
For that reason, employers should audit their handbooks, executive agreements, and prior practice. A pattern of paying two weeks per year of service may be described internally as custom, but employees and courts may treat it as expectation. That is especially sensitive where termination without cause in Maryland affects long-serving staff or senior employees.
When severance becomes legally obligated?
Severance usually becomes binding in three ways (rather than as a rule).
First, the employment contract may expressly promise it. Second, a written severance plan or policy may create a right to payment. Third, mass-layoff notice failures can generate back-pay exposure that functions much like severance even if not labeled as such.
In Maryland, that third point now needs a two-track analysis. Federal WARN can create back-pay liability for covered larger employers, and Maryland’s ESA can impose its own notice obligations for certain smaller reductions in operations. So, when employers talk about the Maryland WARN Act, the accurate 2026 picture is broader than federal WARN alone.
Severance agreements and OWBPA compliance in Maryland
Where the departing employee is 40 or older and the agreement waives age claims, a Maryland severance agreement must satisfy federal Older Workers Benefit Protection Act (OWBPA) requirements. The waiver must be written clearly, refer specifically to ADEA rights, advise the employee in writing to consult an attorney, offer additional consideration, allow at least 21 days for an individual decision or 45 days in a group programme, and provide a 7-day revocation period after signature. U.S. Equal Employment Opportunity Commission (EEOC) guidance sets this out plainly.
If those requirements are missed, the employer may still have paid the money but failed to secure a valid age-claim waiver. That is why severance documents should never be treated as recycled templates.
Severance and unemployment insurance interaction in Maryland
Maryland unemployment guidance focuses heavily on the reason for separation rather than the mere existence of severance. Misconduct, gross misconduct, and aggravated misconduct can delay or block benefits.
That is one reason lump-sum severance pay in Maryland is often cleaner than salary continuation. It usually separates the payment from the employer’s narrative about active employment status and can make the offboarding story easier to administer. It also avoids turning goodwill into a payroll complication.
5. Maryland WARN Act and mass layoff obligations
What many employers call the Maryland WARN Act is not a single Maryland statute, and the 2026 position is more demanding than older summaries suggest. Federal WARN still applies to larger employers, but Maryland’s Economic Stabilization Act (ESA) now separately requires 60 days’ notice for certain reductions in operations involving employers with 50 or more Maryland employees. Maryland Department of Labor WARN page and its ESA FAQ make that clear.
So, in 2026, Maryland’s layoff laws are a combined federal-and-state compliance exercise rather than a single regime. Employers should no longer rely on the older shorthand that Maryland has no state layoff-notice regime.
Federal WARN Act coverage in Maryland
Federal WARN generally covers employers with 100 or more employees, with specific counting rules for part-time and recent hires. It requires 60 days’ advance written notice of covered plant closings and mass layoffs. A mass layoff generally means 50 to 499 affected employees making up at least 33% of the site workforce, or 500 or more affected employees regardless of percentage.
Notice must go to affected employees or their representatives, the state dislocated worker unit, and the local chief elected official. The notice content rules are detailed, which is why employers should draft these notices centrally rather than locally.
Maryland ESA coverage in 2026
Maryland’s ESA applies when an employer with 50 or more employees in Maryland initiates a “reduction in operations.” The Department explains that this includes relocations or shutdowns that reduce headcount by at least 25% or 15 employees, whichever is greater, over a three-month period. It also requires written notice at least 60 days in advance, subject to stated exemptions.
That means Maryland’s layoff laws now reach some employers that federal WARN does not due to lower thresholds and broader scope. For workforce planning, that is one of the most important 2026 developments in termination of employment in Maryland.
Notice requirements for layoffs and plant closings in Maryland
Under federal WARN, employers need to provide clear information about what is happening. This includes where the layoffs are taking place, when they will happen, which roles are affected, and who employees can contact for more information.
Maryland has its own rules under the ESA. These notices must also be shared with affected employees, any union representatives, and local government officials. The state provides guidance on what should be included, so it’s important to follow that separately rather than relying only on federal rules as the requirements are not identical.
For remote and hybrid teams, there is an added consideration. How you define the “workplace” can change the analysis. In areas like the Baltimore–Washington corridor, a distributed team may still be treated as a single workplace depending on how the work is organised.
Exceptions and reduced-notice scenarios in Maryland
Federal WARN allows limited exceptions, such as sudden business downturns, efforts to secure funding, or natural disasters (e.g. unforeseeable business circumstances or faltering company exceptions). Even in those cases, employers are still expected to give as much notice as possible.
Maryland has its own rules under the Economic Stabilization Act (ESA), with similar but separate exceptions that must be assessed independently. Because of this, relying only on a federal WARN analysis can create risk.
In practice, employers should assess both federal and Maryland requirements before making decisions on notice and timing.
6. Wrongful termination in Maryland
Wrongful termination in Maryland is where at-will doctrine meets its limits, and it is usually driven by public policy, discrimination, retaliation, or constructive discharge theories. Employers do not defend these claims with slogans. They defend them with consistent documents, clear chronology, and decisions that match what the record already showed before the dismissal happened.
That is why the strongest defence to disputed termination of employment in Maryland is usually not a better argument after the fact, but a better management record beforehand supported by contemporaneous documentation.
Public policy exception in Maryland
Maryland recognises a wrongful-discharge claim where the dismissal violates a clear mandate of public policy. In practical terms, employers should assume risk where an employee was dismissed after asserting a legal right, refusing unlawful conduct, or making a legally protected report (e.g. whistleblowing or compliance-related reporting).
This is narrower than a general fairness test. An employee still needs a clear legal basis, not just a sense that the dismissal was harsh or unreasonable. But when the facts are bad, the public-policy route can turn an assumedly simple at-will termination in Maryland into litigation exposure.
Discrimination-based termination in Maryland
A dismissal tied to race, sex, pregnancy, disability, age, sexual orientation, gender identity, national origin, or other protected traits is unlawful regardless of at-will status. The question in practice is usually whether the employer can show a genuine, non-discriminatory reason that existed before the decision.
That is why weak performance documentation is so dangerous. Where the written record is thin, inconsistent, or created only after the employee complains, wrongful termination in Maryland becomes much easier to allege and much harder to defend.
Retaliation claims in Maryland
Retaliation claims are often more dangerous than the underlying complaint because timing alone can create a plausible narrative of adverse action linked to protected activity. A dismissal shortly after a wage complaint, protected leave, accommodation request, or participation in an investigation will attract scrutiny from regulators or courts.
Employers should therefore pause before any adverse action taken within the months after protected activity and conduct a documented review of the decision-making process. That review step is a core part of a defensible Maryland employee termination process.
Constructive dismissal in Maryland
Constructive dismissal (constructive discharge) means conditions become so intolerable that a reasonable employee would feel compelled to resign. It is difficult to prove, but it is often pleaded where there has been humiliation, pay cutting, isolation, or a strategic stripping of duties or other materially adverse changes to working conditions.
For employers, the lesson is straightforward. A resignation does not always end risk. A forced-feeling exit can still produce wrongful termination in Maryland allegations if the surrounding conduct would have made a direct dismissal legally suspect.
7. Fixed-term contract exits in Maryland
The end of a contract in Maryland is not analysed the same way as an ordinary at-will exit. When a fixed-term contract expires naturally, the relationship usually ends because the agreed term ended. When the employer cuts the term short without contractual authority, the issue is usually breach of contract rather than ordinary at-will dismissal.
That distinction matters for damages, notice, and renewal risk. Employers using project contracts, grant-funded roles, or contractor-facing programme appointments should build the exit terms into the agreement before the relationship begins including termination rights, notice provisions, and any early-exit mechanisms.
End of term vs early termination in Maryland
At the end of a contract in Maryland, expiry on the agreed date usually does not require cause. But employers should still give written non-renewal notice where the contract is silent, because allowing the employee to continue working can create ambiguity about renewal or a shift back to at-will status.
Early termination is different. If the contract does not allow it, ending the relationship before the term expires can expose the employer to the employee’s remaining economic loss, subject to mitigation (i.e. the employee’s duty to seek alternative employment). That is a very different risk profile from at-will termination in Maryland.
Liquidated damages and early-exit clauses in Maryland
A well-drafted early-exit clause can give employers commercial certainty. The amount should represent a reasonable estimate of anticipated loss at the time of contracting, not a punishment or penalty. The more extreme the clause, the more likely it is to be challenged.
Where the contract also contains notice language, the employer should align the non-renewal date, final pay timing, and return-of-property steps inside one coherent Maryland employee termination process. Otherwise, a contract exit becomes administratively messy and harder to defend in the event of dispute.
Federal contractor programme termination in Maryland
Maryland employers near the National Capital Region often face programme endings tied to federal contracts, option non-renewals, or convenience terminations. In those cases, the employment analysis often depends on whether staff can be redeployed, whether a successor contractor must offer work under the federal Service Contract Act (SCA), and whether the timing triggers WARN or ESA notice duties.
That makes federal contractor exits a distinct subcategory of termination of employment in Maryland. The employment answer cannot be separated from the procurement and programme answer.
8. Post-termination obligations in Maryland
Ending the job does not end the employer’s legal work. Post-exit restrictions, confidentiality, property return, and benefits continuation are all part of lawful termination of employment in Maryland. The most common error is treating offboarding as an IT task rather than a legal and operational process.
That is particularly true for senior staff, sales teams, healthcare personnel, and anyone with access to data, pricing, code, or client relationships or other sensitive business information.
Non-compete enforceability after exit in Maryland
Maryland now voids non-competes for employees earning at or below 150% of the state minimum wage (threshold updated periodically based on minimum wage changes), and for certain direct-care health roles earning 350,000.00 USD or less. For higher-paid direct-care health professionals, the restriction may not exceed one year and 10 miles from the primary place of employment as defined under Maryland General Assembly, §3-716.
That means enforcement strategy should be selective. Employers should reserve injunction efforts for cases involving a real business interest, not use them as routine punishment at exit.
Employers should also remember that enforceability is only part of the question. The commercial value of enforcement matters just as much. A narrowly drafted restriction tied to client relationships, confidential information, or team stability is easier to defend than a broad attempt to block future work which may be deemed unenforceable.
In practice, the strongest approach is to assess the employee’s role, access, and competitive risk before threatening enforcement.
Non-solicitation obligations in Maryland
Customer and employee non-solicitation clauses are often easier to defend than broad non-competes, but they still depend on careful drafting and timely enforcement. Delay can damage the argument that urgent court relief is necessary.
As part of the Maryland employee termination process, employers should remind the departing employee of any surviving solicitation restrictions in writing at the time of exit. Silence invites later factual disputes.
Employers should also make sure those clauses are operationally usable, not just legally present. A restriction that clearly identifies protected customer groups, restricted conduct, and time limits is easier to monitor and enforce after departure.
That matters in Maryland because many post-exit disputes do not begin with obvious poaching; they begin with LinkedIn outreach, informal contact with former colleagues, or quiet client migration that the employer notices too late.
Confidentiality and trade secret protection in Maryland
Confidentiality duties should be reinforced at exit, not assumed. Employers should collect devices, disable cloud access, confirm return or deletion of files, and document that reminder in the exit record as part of a defensible process.
Where genuinely sensitive information is involved, the employer should also monitor for post-exit misuse rather than waiting for damage to become obvious. In senior exits, this is as important as getting Maryland’s final pay rules right.
Employers should also distinguish between ordinary confidential information and material that may qualify for trade secret protection. The latter usually requires more than a generic reminder at departure. It depends on whether the business has taken reasonable steps to preserve secrecy throughout the employment relationship.
Access controls, confidentiality clauses, download restrictions, and clear internal classification all strengthen the employer’s position if enforcement becomes necessary after exit.
Return of company property in Maryland
Maryland law does not give employers a simple wage-deduction shortcut for missing property. Because wage deductions are tightly limited, employers should recover property through process, written demand, and, if needed, civil action rather than by improvising payroll deductions.
That is why access cards, laptops, phones, keys, and account credentials should all sit on one offboarding checklist. Property recovery is not an afterthought to termination without cause in Maryland or termination for cause in Maryland. It is part of the exit itself.
9. COBRA and benefits continuation in Maryland
Benefits continuation is a core end-of-employment issue, not an administrative footnote. Federal COBRA applies to many larger employers, while Maryland continuation rules can apply to insured group contracts even where federal COBRA thresholds are not met, depending on the policy type. The employer should therefore decide benefits timing at the same time it decides dismissal timing and ensure alignment with plan terms and legal requirements guidance and Maryland Insurance Administration materials are the key official references.
This is one area where a sloppy offboarding can create avoidable ERISA compliance risk, benefits disputes, and employee-relations issues even where the dismissal itself was lawful.
Federal COBRA obligations in Maryland
COBRA generally applies to employers with 20 or more employees on a typical business-day basis during the prior calendar year. The employer must notify the plan within 30 days after the qualifying event, and the plan must then send the election notice within 14 days. Qualified beneficiaries then have at least 60 days to elect coverage and 45 days after election to make the first premium payment.
Termination for gross misconduct can block COBRA, but that phrase is interpreted narrowly. Employers should not assume that every serious disciplinary dismissal automatically defeats benefits continuation.
Maryland continuation coverage
Maryland continuation rules can apply to insured group contracts without a 20-employee minimum, according to the Maryland Insurance Administration’s comparison chart. For termination-of-employment events, continuation of up to 18 months may apply, subject to specific qualifying conditions and notice requirements.
So, while people often refer loosely to “mini-COBRA”, the better approach is to check the Maryland Insurance Administration materials for the specific policy type and qualifying event. That is particularly important for smaller employers navigating the end of a contract in Maryland or a non-cause exit for the first time without prior U.S. benefits experience.
Timing of benefits termination in Maryland
Health cover should not be cut off carelessly in the middle of a paid coverage period. The employer should confirm the last active-coverage date, notify the carrier or administrator immediately, and ensure the termination letter matches what the plan will do.
This should sit beside final wages and severance in the same exit plan. A clean dismissal can still become a dispute if the employee is told one thing in the meeting and receives different benefit paperwork later.
10. How CXC manages Maryland end of employment?
Ending employment in Maryland needs to be handled carefully. Small mistakes around timing, pay, or documentation can quickly create issues.
When you partner with CXC, exits are managed as a structured process, not an ad hoc HR task. Final pay is handled on time, notice requirements are checked early, and separation terms are set up clearly.
This includes managing things like severance terms, post-employment restrictions, and required notifications in a way that fits Maryland rules.
The focus is on getting each step right. That reduces risk, avoids rework, and makes sure the process is handled properly from start to finish.
Compliant offboarding for EOR engagements in Maryland
With CXC, you get an offboarding process built around Maryland’s actual deadlines and exposure points. Final wages are aligned to Maryland’s final pay rules, benefits continuation is tracked against federal and state timing, and the written record is organised from the start rather than assembled defensively later.
That matters when your internal team is overseas or unfamiliar with the difference between ordinary dismissals and mass-reduction notice events in Maryland.
Reducing wrongful termination risk in Maryland
CXC reduces risk by building the evidence trail before the exit. Performance records, manager communications, disciplinary steps, and rationale are all aligned so that if wrongful termination in Maryland is later alleged, the file already tells a coherent story.
That proactive discipline is especially valuable where the employer is considering termination for cause in Maryland, where the label itself can affect benefits, severance posture, and litigation risk.
That matters because most termination disputes are not decided by whether the employer can describe a lawful reason after the event. They are shaped by whether the records show a consistent decision-making process before the exit happened.
Where the documentation is thin, contradictory, or created only after concerns are raised, even a manageable dismissal can become harder to defend and more expensive to resolve.
Managing federal contractor exits in Maryland
CXC is also equipped for the Maryland-specific reality of federal program endings and contract rebids. That includes checking whether federal WARN, ESA, or both apply, deciding whether redeployment is realistic, and managing the employment consequences of contract termination without losing control of the timeline.
That is where a generic offboarding model usually fails. Maryland exits tied to government contracting need a workforce partner that understands both the local employment rules and the program context in which they operate.
Hiring in Maryland? Speak to our team to keep things compliant from the start.
Grow your team. We’ll handle the rest.
Expanding your team shouldn’t mean expanding your workload. With CXC’s Human+ model, we combine intelligent automation with hands-on expertise to make global hiring effortless. From onboarding to payroll, every process runs smoothly, accurately, and compliantly, so your people can hit the ground running from day one.
While we take care of the details, you can focus on what matters most: growing your business and empowering your teams to succeed anywhere.
Australia/New Zealand Head Office
Asia Head Office
EMEA Head Office
North America Head Office
Latin America Head Office
Level 3, 99 Walker Street
North Sydney, NSW 2060 Australia
