# Welcome Welcome to the seSQue Payroll user guide. Here you'll find helpful resources to assist you in navigating and using the software effectively. We regularly review these pages to keep them up to date. If you notice anything missing or outdated please [let us know](https://www.sesque.com#contact). If you have suggestions for new features, improvements or fixes - or would like to vote on ideas suggested by others - visit our [Product Improvements](https://sesque.canny.io/product-improvements) board. # Register new account Follow the steps below to register a new account with seSQue: Go to , enter your *Email* and *Password* (confirm your password), then click on the `Sign Up` button*:* ![](https://2379102928-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lrq9oeKSkBYyajIcEKm%2Fuploads%2FM87Jzo7A0s46PKLq8nHg%2Fimage.png?alt=media\&token=6e5cd4da-8d0c-4367-b622-e15a7cb14ff2) An account confirmation link will be emailed to you. ![](https://2379102928-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lrq9oeKSkBYyajIcEKm%2F-MS9xs_aRkRD89Lo9bxu%2F-MSAEYeVbMMokFrAkVEA%2Fimage.png?alt=media\&token=ddae3d66-a45e-47bc-885b-7b2060223bfb) Find the email in your *Inbox*, if not there make sure to check your *Spam* folder too, and click on the provided link: ![](https://2379102928-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lrq9oeKSkBYyajIcEKm%2Fuploads%2FF5ghtoMGZ08eR1yFFmDR%2Fimage.png?alt=media\&token=ce3b77fd-4235-4303-aea5-aeb28602b8bd) That's it, your new seSQue account is ready. Just click on the `Proceed to your account` button to start using it. # Setting up payroll On your first login you will be prompted to set up your new account:

Click on the *Account setup required* link and follow the step-by-step instructions on the screen. The first step determines the type of account you are creating: * users reporting for their **own business** are creating **regular** accounts (*Basic* subscription initially, with the option of upgrading to the *Advanced* subscription later on) * users reporting for **other businesses** are creating **agent** accounts (*Ultimate* subscription) {% hint style="warning" %} The type of account **cannot be changed** once the initial setup is finalised. {% endhint %}

Enter your user details, then click `Next`:

Enter your business details, then click `Next`:

When creating an *Agent* account for reporting STP on behalf of your customers, you must enter **your own business details** on this page (your customers will be set up separately, after this setup is finalised):

If an *Agent* account was created, the setup is concluded:

If a *Regular* account was created, the setup is finalised by confirming your STP details*:* {% hint style="info" %} Before you submit STP reports you must register your new [Software ID](/payroll/software-id) with the ATO, to let them know that SESQUE PTY LTD is your new payroll provider. Find out more details [here](/getting-started/register-payroll-provider). {% endhint %} {% hint style="warning" %} If you have already lodged STP reports from another system this financial year, you must decide what to do with your existing ATO data. There are several different options at your disposal, each with its own pros and cons. Find out more details [here](/payroll/changing-payroll-providers). {% endhint %}

Lastly, click `Finish` to start using the system. # Register payroll provider Before submitting STP reports you must register seSQue as your payroll software provider with the ATO. There are two options available, both of them require your [Software ID](/payroll/software-id). ## By phone Call the ATO on 1300 852 232 and inform them that you would like to nominate seSQue as your payroll software provider. You will be asked to provide the following information: * Software provider name: SESQUE PTY LTD * Software provider ABN: 53628625641 * Your [Software ID](/payroll/software-id) ## Online You can register online using ATO's [Access Manager](https://am.ato.gov.au/). {% hint style="info" %} Note that you will need [myGovID](https://www.mygovid.gov.au/) to log in. {% endhint %}

Select *My hosted SBR software services* on the side menu, then click on the `Notify the ATO of your hosted service` button:

Find seSQue either by name SESQUE PTY LTD or by ABN 53628625641 and select it as your service provider:

Add your [Software ID](/payroll/software-id) and click *Next*:

Review your changes and click `Save` when you are ready:

# Adding your payees Now that your payroll is set up, the next step is to add your payees. Locate the *Payees* link on the side panel, then click on the `New payee` button:

Enter your payee's details:

Note that the we currently support two types of payees: * arm's length employees and * closely held payees. It is important to choose the correct type of payee for your scenario, since these are being reported to the ATO under different income stream types: {% hint style="info" %} Some concessions are available to small employers making payments to closely held payees, such family members of a family business, directors and shareholders of a company or beneficiaries of a trust, most notable being: * quarterly reporting and * finalising later than 14 July. {% endhint %}

Note as well the `Is director` flag in the screenshot above. Turning this flag ON will enable *Director's fees* payments for this payee. Once you are done setting up all the payee's relevant fields remember to click `Save` :

Repeat this process for all your payees. # Lodging your first pay run Having added your payees, you are now ready to submit your first pay run. Start by clicking on the *Pay runs* link on the side panel, then on the `New pay run` button:

Adjust the pay run details according to your specific scenario: {% hint style="info" %} The *Pay cycle* field is of particular importance. The system uses it to: * calculate the *Start date*, whenever the *End date* changes and * filter the list of available employees, e.g. *Weekly* pay cycles list only the employees paid weekly, *Monthly* pay cycles list only employees paid monthly and so on {% endhint %}

Add all the payments made to your payees and click `Save` when done. Then submit the pay run to the ATO by clicking on the `Lodge with ATO` button: {% hint style="warning" %} In order to ensure a successful pay run lodgement, please consider the following advice from the ATO. To satisfy the STP reporting obligations of the payer: * lodgements must be submitted on, or before, the date the payment is made and * lodgements must contain at least one payee record and * payee records must include both tax withheld and superannuation entitlement information {% endhint %}

Lodgements are usually processed in a couple of minutes. Once the processing completes, the result will be available in the notifications section: {% hint style="info" %} Click on the :bell: to view your current notifications. *Dismiss* old notifications, once they are no longer relevant. {% endhint %}

Alternatively, you can retrieve your pay run record and check the status in there:

In case your lodgement failed you can reopen the pay run, make any necessary corrections, and resubmit it to the ATO:

# BMS ID The Business Management System (BMS) ID is a unique identifier used by the ATO to determine the payroll software that created the data in a pay event. It accommodates businesses with more than one simultaneous payroll system and facilitates changing payroll systems throughout the financial year. In seSQue Payroll the BMS ID can be found at the tax branch level.

Changing the BMS ID must be carefully planned. The ATO displays the payee data grouped by ABN/Branch/BMS ID/Payroll ID. If any of these key identifiers change, the ATO will create a separate payee record. # Software ID The Software ID is a unique identifier used to distinguish each subscription or instance of software. It is automatically generated by the system during the [payroll setup](/getting-started/setting-up-payroll) and you must [register it with the ATO](/getting-started/register-payroll-provider) before submitting reports. In seSQue Payroll the Software ID can be found at the subscription level:

# TFN exemptions When a Tax File Number (TFN) was not provided employers must use one of the following exemption codes:

Code	When to use
`000000000`	Use if the payee has not provided a TFN or fails to provide one within 14 days.
`111111111`	Use if a payee does not provide a valid TFN or you receive a declaration from the payee which says they have applied for a TFN. This code should be updated with the payee’s TFN, or, with the no TFN quoted code when the payee fails to provide the TFN to the payer within the 28-day period allowed.
`333333333`	Use if a payee is under 18 years old and claims the general exemption because they don't earn enough for tax to be deducted. If circumstances change and the payee subsequently earns a level of income that attracts tax, a TFN will be required to be provided at that time.
`444444444`	Use if the payee is a recipient of a social security or service pension or benefit (other than Newstart, sickness allowance, special benefits or partner allowance) and an exemption from quoting a TFN may be claimed.

# Changing payroll providers Changing payroll providers during a financial year must be planned carefully. Implemented incorrectly, it may lead to data duplication on the ATO side. You can choose one of the following three processes we support at the moment. ### 1. Finalise existing payee records with your old payroll provider and start fresh with us :thumbsup: straight forward process\ :thumbsdown: two separate Income Statements per payee (one for each payroll provider) The fact that two separate Income Statements are created must be communicated to your payees. Not being aware that there are multiple Income Statements to include when submitting their Income Tax Return may lead to potential issues at the end of the financial year. The actual process is fairly straight forward. Finalise the existing payee records with the old payroll provider first, then keep the new [BMS ID](/payroll/bms-id) automatically generated by our system and you are ready to start STP reporting with seSQue Payroll. {% hint style="warning" %} Failing to finalise the existing payee records with the old payroll provider, before making your first STP lodgement in seSQue Payroll, may lead to data duplication on the ATO side. {% endhint %}

### 2. Zero out existing payee records with your old payroll provider and bring over your payees' opening balances :thumbsup: one Income Statement per payee\ :thumbsdown: tedious process, having the enter all payees' opening balances This is the method preferred by the ATO. You must first zero out the existing payee records with your old payroll provider. Then you must keep the new [BMS ID](/payroll/bms-id) automatically generated by our system and while adding your payees enter their opening balances too. The first successful STP lodgement in seSQue Payroll will bring your payees' ATO balances back to date. {% hint style="warning" %} Failing to zero out the existing payee records with the old payroll provider, before making your first STP lodgement in seSQue Payroll, will lead to duplicated payee records on the ATO side. {% endhint %}

### 3. Keep BMS ID and payee identifiers (Payroll ID) issued by your old payroll provider and bring over your payees' opening balances :thumbsup: one Income Statement per payee\ :thumbsdown: error prone process, incorrect/mistyped identifiers will lead to duplicated ATO payee records This method is not favoured by the ATO, because it defeats the purpose of the [BMS ID](/payroll/bms-id) to uniquely identify the source of all pay events throughout the financial year. Thus it should only be used as a last resort, for out of the ordinary scenarios such as having no access to the old payroll provider system. In respect to the actual process, there is nothing to be done on the old payroll provider's side. However, things get more elaborate on our side. First, you must replace the [BMS ID](/payroll/bms-id) automatically generated by our system with the [BMS ID](/payroll/bms-id) issued by your old payroll provider. {% hint style="info" %} Note that the format we have chosen for our BMS ID is the Globally Unique Identifier (GUID). Therefore, this option will only work if your existing BMS ID is also compliant with [RFC 4122](https://datatracker.ietf.org/doc/html/rfc4122). {% endhint %}

Later on, when adding your payees, you must use the Payroll IDs issued by your old payroll provider. {% hint style="warning" %} Failing to use both the BMS ID and the Payroll IDs issued by your old payroll provider will lead to duplicated payee records on the ATO side. {% endhint %}

Last but not least, you must enter your payees' opening balances, so that STP reporting can continue from where you left off with your old payroll provider. # Correct lodged pay runs Although seSQue Payroll is quite flexible, allowing you to make any changes you want to your existing pay runs, sending these amendments to the ATO may not always be straight forward due to the various conditions which apply depending on the type of correction being made (see the ATO's article [Correcting information reported through STP](https://www.ato.gov.au/Business/Single-Touch-Payroll/In-detail/Single-Touch-Payroll-employer-reporting-guidelines/?anchor=BK_5Correctingapayeventreport) for more information). In seSQue Payroll there are two options for dealing with pay run corrections, reopening an entire pay run and reopening only specific employee records inside a pay run. The former should be used for dealing with major issues and the latter for minor, less critical issues. Reopening a successfully lodged pay run must be considered carefully. Reopened pay runs are sent to the ATO as full file replacements (FFR). An FFR provides the ability to replace the **latest pay run lodgement** that was sent to the ATO in error or contains significant corrupt data. To reopen a pay run use the `Reopen` button: {% hint style="warning" %} Be aware that the ATO: * will reject an FFR if any employee data sent in the original submit action has been changed by a subsequent pay run, or payment summary, lodgement * only accepts **one FFR per day** {% endhint %}

When reopening already lodged pay runs some fields remain read only, e.g tax branch, pay date, in order to avoid potential data duplication on the ATO side. {% hint style="warning" %} If the error is related to one of these read only fields [contact us](https://www.sesque.com/#contact), we may be able to assist you. {% endhint %}

Note as well that removing a pay run from seSQue Payroll does not affect your ATO existing records. To undo a previously successful ATO lodgement, a possible approach may be to reopen the affected pay run, zero out the included payees' data and resubmit the pay run to the ATO:

Once you confirm that all your payee YTD balances are correct on the ATO side, then you may proceed with the removal of the respective pay run from seSQue Payroll. A less constrained alternative, which will work for any pay run, not just the latest lodgement, is to reopen just the affected payee records inside a pay run. On resubmitting the pay run, only the updated payee records will be sent to the ATO. To reopen a payee record, start by editing the pay run using the `Edit` button:

Then use the `Reopen` button next to the payee record you want to change: {% hint style="warning" %} Note that on resubmitting the pay run to the ATO, this update will now become your latest lodgement. As a result, any further full file replacement (FFR) attempts will be rejected until a new pay run is lodged. {% endhint %}

Lastly, keep in mind that you can sometimes correct issues in your next cycle pay run, provided that this falls within the current financial year. You can make adjustments to any number of pay runs, either by reopening entire pay runs or only specific payee records, and `Lock amounts without lodging`. Then later on, whenever you lodge your next cycle's pay run, all these locked amounts will be reflected in the year-to-date (YTD) balances of the payee records sent to the ATO.

# Finalisation declaration At the end of each financial year payers must notify the ATO that they have finished reporting for all their payees. This is called the *finalisation declaration* and must be submitted to the ATO by either **July 14th** for arm's length employees or **September 30th** for closely held payees. {% hint style="info" %} If you only have closely held payees, you have until the due date of the closely held payee’s individual income tax return to make the finalisation declaration, which usually is **October 31st**. {% endhint %} In seSQue Payroll this can be done from the payment summary of the financial year. Go to *Payment summary* and find the financial year you want to finalise:

Edit the payment summary, add the required payees and review their amounts:

Then click `Save` when you are ready:

Click on the `Finalise STP` button to instruct the ATO to mark the records of the nominated payees as **tax ready** for the given financial year:

Note that you do not necessarily have to finalise all your payee records at the same time. You may choose to add payees to the payment summary gradually, as their records become tax ready. Each time your click on the `Finalise STP` button, the system will submit to the ATO only the unlocked payee records, skipping the already finalised ones:

Lastly, after all your payee records have been finalised for a given financial year, you may want to lock the payment summary to prevent further changes. To do that, expand the `Finalise STP` split button and select `Lock payment summary`:

Once that is done, the system will prevent further changes to this particular payment summary. Note however, that you still have the option to reopen this payment summary later on, if more changes are required:

# Leave tracking The *Advanced* and *Ultimate* editions of seSQue Payroll have the ability to track an employee's leave balances. All new accounts come predefined with a list of leave types. You can customise this list to suit your specific requirements. Navigate to the *Business* settings section on the side menu and `Edit` your business:

The list of existing leave types is found in the *Leave* tab page. You can edit/delete existing leave types and also add new types as required. {% hint style="info" %} Note that certain leave types, such as annual leave or sick leave, cannot be deleted. {% endhint %}

You can sort the leave items by dragging and dropping them in your preferred order. After you save the changes, the order will be persisted in all the dropdowns throughout the system.

For each leave type you can specify the STP category to be sent to the ATO, the number of hours accrued per year (by a full-time employee), whether or not to show the leave balance in payslips and more. {% hint style="info" %} Note that some settings only apply to certain leave types. {% endhint %}

You can also set up an employee's leave entitlements, so that they accrue leave automatically with every processed pay run. This is done in the *Payees* section. Select the employee from the list and `Edit` their record:

Then navigate to the *Leave balances* section and assign the leave types which apply, specifying the number of hours accrued per year (for part-time employees manually adjust the value according to the number of hours they work) and the employee's current balance: {% hint style="info" %} Note that leave balances only apply to full-time and part-time employees. {% endhint %}

Now each time this employee is included in a pay run, the system automatically calculates the number of hours to be accrued and includes them in the pay run. You can manually adjust these records generated by the system.

Last but not least, an employee's leave balances may be shown in their payslip. This is controlled individually for each type of leave (see the *Business* settings section above).

# Payslips Payslips are a legal requirement for employers in Australia. They must be given to employees within one working day of being paid, in either electronic or hard copy format. To assist with this requirement, seSQue Payroll provides the ability to generate payslips in PDF format directly from the pay run: {% hint style="info" %} Note that this feature is only available in the *Advanced* and *Ultimate* subscriptions. {% endhint %}

The generated PDF payslips can be viewed online using the `Payslip viewer`. They can also be saved locally for subsequent processing (e.g. printing, emailing) or can be emailed to the employees straight from the system:

Note that penalties apply for providing false or misleading information on payslips. To avoid potential issues, always generate payslips after you lodge your pay runs with the ATO. That will ensure the data you provide to your employees is up to date. As a way of enforcing this best practice, we have made payslips unavailable for unlocked pay run / employee records. {% hint style="warning" %} Remember to regenerate the relevant payslips if you reopen a pay run / employee record. {% endhint %} # ABA file downloads Australian Banking Association (ABA) file format, sometimes called Direct Entry or Cemtext, is commonly used by Australian Banks to process batch transactions. An ABA file (\*.aba) uses the ASCII character encoding to store data which can be uploaded into the Internet Banking systems. The Advanced and Ultimate editions of seSQue Payroll can generate these files for you from your lodged pay runs. This functionality can be enabled from the *Business* settings section. `Edit` your business record and look for the `Generate payment files` toggle in the *General* tab page: {% hint style="info" %} Before enabling this feature make sure your payroll bank account is defined in the *Banking* tab. If not present, add it and `Save` before turning the toggle ON. {% endhint %}

Turn the toggle ON, fill in the details as advised by your financial institution and `Save` when done: {% hint style="info" %} Some Australian banks provide generic APCA (Australian Payments Clearing Association) ID numbers you can use when submitting ABA files: * ANZ - `000000` * CBA - `301500` * NAB - `000000` * Westpac - `037819` You should always confirm with your bank, as they may provide a specific APCA ID (sometimes called a Direct Entry User ID) unique to your business. {% endhint %}

Then move on to your *Payees* and ensure you have their bank account details recorded:

And finally, go to *Pay runs* and look for the `Download ABA file` button on your lodged pay runs:

A generated ABA file will look similar to this: {% hint style="info" %} Note that this sample file does not contain a self-balancing transaction. {% endhint %}

The transaction description that appears on your own bank statement will follow this format:\ `PAYROLL` For example, for a monthly pay run with a pay date of 4 January, the description will be `PAYROLL0401M`. Your employees will see the following transaction description on their bank statements:\ `SALARY ` For example, for an employee with the number EMP00001, the description will be `SALARY EMP00001`. # Funds Making superannuation fund details available in the system is a two step process. First, you must add the superannuation funds your business works with. To do that, select the *Business* entry from the side menu and `Edit` your business:

Select the *Superannuation* tab page, click `Add super fund` and add your superannuation fund to the list, then click `Save` when done: {% hint style="warning" %} If you are planning to use our Beam integration to process your employees' [super contributions](/super/contributions), please make sure your APRA-regulated funds have their USI. Beam requires the USI in order to process contributions successfully. {% endhint %}

All the active superannuation funds will then be available for selection at the payee level. To set up a payee's superannuation fund, start by selecting *Payees* from the side menu and `Edit` the required employee record:

Then go to the *Superannuation* tab page, select the payee's superannuation fund from the list and click `Save` when done:

# Member Verifications Member verification is a new requirement introduced as part of [Payday Super](https://www.sesque.com/articles/payday-super-for-small-business). This is performed by sending a **Member Verification Request (MVR)** to the payee's super fund. In [seSQue Payroll](https://www.sesque.com/), member verifications are managed from the payee's *Superannuation* tab. To verify a payee's membership with their super fund, follow these steps: 1. Open the payee record. 2. Select the *Superannuation* tab. 3. Confirm that the payee's superannuation details are correct. 4. Click on the `Verify Membership` button. 5. Wait for the verification result. Most super funds respond within 24 hours.

A successful verification is required before the first contribution to a payee's chosen super fund. You may request another verification if details that may affect the payee's identification by the super fund have changed, for example the payee's name, date of birth, member number or chosen super fund. Verification should **not** be used as a routine check before every contribution. Each member verification progresses through one of the following statuses. {% hint style="info" %} The current status is indicated throughout the system by a colour coded `MVR` badge. {% endhint %}

Status	Badge	Description
Pending	MVR	The member verification request has been submitted successfully and is awaiting a response from the super fund.
Unmatched	MVR	The super fund could not verify the payee's membership. Review the verification errors, correct any issues where appropriate and request another member verification if required.
Indeterminate	MVR	The super fund could not complete member verification. This commonly occurs while super funds are transitioning to Payday Super and are not yet able to process Member Verification Requests (MVRs). You may submit the contribution. Continue to monitor notifications, as the super fund may still reject the contribution.
Matched	MVR	The payee's membership was successfully verified. You can proceed with their first super contribution.

To view the details of a member verification, including any errors, warnings or additional information, click its `Status` button.

On the *Super Contribution* page, use the MVR badges to quickly identify payees whose member verifications may require attention before submitting a contribution. Ideally, all payees should display a green MVR badge, indicating that their memberships have been successfully verified, before you submit a contribution. The exception is payees for whom successful contributions have previously been submitted via [seSQue Payroll](https://www.sesque.com/), as this confirms that the member is already known to the fund. {% hint style="warning" %} **Important:** Before submitting a contribution, review the MVR badges for all payees. * **Pending (less than 24 hours)**: Wait for the super fund to respond before submitting the contribution. * **Pending (24 hours or more)**: You may submit the contribution and we will pass it to Beam for further processing. However, monitor your Beam notifications, as the contribution may still be rejected by the destination fund. * **Indeterminate**: You may submit the contribution and we will pass it to Beam for further processing. However, monitor your Beam notifications, as the contribution may still be rejected by the destination fund. * **Unmatched**: Review the member verification details, correct any issues and request another member verification before submitting the contribution. {% endhint %}

When you submit a contribution, [seSQue Payroll](https://www.sesque.com/) checks whether each payee meets the member verification requirements. If one or more payees require member verification, the contribution will not be submitted and a notification will explain the issue.

After resolving any member verification issues and waiting for pending verification requests to complete, submit the contribution again. # Contributions seSQue Payroll has partnered with [Beam clearing house](https://beamconnect.com.au/partners/sesque/) to offer automated superannuation payments to our paid subscribers. The *Beam super payments* integration is listed under *Settings* -> *Integrations* in the side menu.

This is an opt-in service. To start the enrolment process of your business click on the `Activate` button. {% hint style="warning" %} Before activating the service we recommend you check your business details in seSQue Payroll (see *Settings -> Business*) to ensure that you have a **default superannuation fund** and, in case you plan to set up Beam with direct debit, a **bank account**. {% endhint %}

This will take you to Beam's website to complete the registration. The registration process requires you to provide information about your business. In order to facilitate this process, we will pre-populate all the relevant fields in Beam for you. {% hint style="warning" %} Any changes you make in Beam to the business details we are sending on your behalf will not be reflected back to seSQue Payroll. If you must make changes, we recommend you do them in seSQue Payroll, before starting your Beam registration. {% endhint %}

At the end of the registration process you will be transferred back to seSQue Payroll.

Upon successful registration, a new entry called *Superannuation* will be added to the side menu. You can use this to make new contributions or view the status of existing ones.

Adding superannuation contributions is pretty straight forward. Start by selecting the contribution cycle and the end date, the list of superannuation accruals will be updated to reflect the specified date range. Select the super guarantee contributions (SGC) and the employer extra contributions (RESC) you want to include, then click `Save` when ready. {% hint style="warning" %} Before adding your first superannuation contribution, make sure you have a bank account set up for your business (check *Settings* -> *Business -> Bank accounts*). You will have to nominate one to be used for refunds, in case your contribution cannot be processed successfully. {% endhint %}

You will notice that the contribution is now displayed grouped by superannuation fund, which is how Beam expects data to be sent. To submit the contribution batch click `Lodge with Beam`.

Alternatively, you can validate contribution batches before submission with `Validate with Beam`. This is recommended in the beginning, to avoid failed lodgements. Beam has a few requirements stricter than seSQue Payroll. For instance, they require the date of birth for all the payees included in a contribution batch.

Details of any warnings or errors raised during data validation can be accessed by clicking on the buttons provided in the *Status* column. {% hint style="warning" %} Contribution batches having errors are rejected by Beam. Contribution batches having warnings are accepted by Beam, but may be rejected at a later stage by the superannuation fund. {% endhint %}

Contribution batches accepted by Beam will be marked as pending and, depending on the payment type, may contain payment instructions.

If all goes well, your contribution will progress through various stages, until it is successfully sent to the destination superannuation fund. In case anything goes wrong, the contribution is rejected and any payments made will be refunded to your nominated bank account. Last but not least, we have made a couple of reports available to help you stay on top of your superannuation obligations.

# Update personal details Select *Administration* from the dropdown menu on the top right corner of the screen:

Go to the *Personal* tab page, enter your name, then click on the `Save changes` button:

# Change password Select *Administration* from the dropdown menu on the top right corner of the screen:

Go to the *Password* tab page, enter your current password, the new password and confirm the new password, then click *Change password*:

# Setup two-factor authentication Select *Administration* from the dropdown menu on the top right corner of the screen.

Go to the *Two-factor authentication* tab page and click on the `Add authenticator app` button.

Follow the instructions on screen and click on the `Verify` button.

A set of recovery codes will also be issued to you. Store these codes in a safe place, you will need them in case your authenticator app stops working or you do not have access to your device. {% hint style="warning" %} Each recovery code can only be used once. {% endhint %}

You can renew your recovery codes by clicking on the `Reset recovery codes` button. {% hint style="warning" %} New recovery codes replace and invalidate all existing codes. {% endhint %}

Using the `Reset authenticator app` button you can set up your authenticator app again if it stops working or you get a new device. Resetting also invalidates the codes from your old device, helping you protect your account if your mobile is lost or stolen.

# Subscriptions seSQue Payroll works with two types of accounts: * regular - for users reporting for their **own business** * agent - for users reporting on behalf of **other businesses** {% hint style="warning" %} The type of account is selected during the initial setup. Find out more in [setting up payroll](/getting-started/setting-up-payroll). {% endhint %} There are two subscriptions for **regular** accounts: * Basic - for single employee micro businesses * Advanced - for small business owners There is one subscription for **agent** accounts: * Ultimate - for accountants, bookkeepers, tax agents etc. The account type can be found under *My Account* in the *Administration* section:

The current subscription details are available on the *Subscription* page in the *Payroll* section:

To upgrade/downgrade the subscription plan of a regular account click `Edit`, then select the new subscription plan and click `Save` when done: {% hint style="warning" %} Note that only one subscription type change, either upgrade or downgrade, is accepted per settlement cycle. {% endhint %}

Upgrading to a paid subscription requires a payment method to be selected. If none is available, you can add one by selecting *Payment methods* from the dropdown menu on the top right corner of the screen:

In the *Payment methods* page click on the `Edit` button:

Then click `Add card`, enter your credit card details and click `Add`, then click `Save` when done:

Last but not least, note that *Ultimate* subscription upgrades/downgrades are disabled for both regular and agent accounts. This does not mean that they are not supported. Feel free to [contact us](https://www.sesque.com/#contact) to discuss your requirements.