Cut double entry with Miter and Premier

Miter’s documentation confirms that journal entry CSVs can be generated from Miter and uploaded to Premier. How Premier handles a duplicate CSV upload is a Premier-side behavior. Check with your Premier administrator or Premier’s support team for guidance on how to prevent or catch duplicate imports. During Miter onboarding, your implementation team can help you establish an export workflow that reduces the risk of sending the same file twice.

If your organization runs multiple legal entities or companies across both Miter and Premier, you will need to configure the integration separately for each entity. The connection setup links one Miter company instance to one Premier company, so GL accounts, departments, projects, and cost codes are managed per entity. Contact your Miter customer success team to discuss how multi-entity setups are handled and what the recommended configuration looks like for your org structure.

When Premier cost codes sync into Miter via API, they appear as activities in Miter. The link between a Miter activity and its corresponding Premier cost code is maintained through a shared primary key: the Miter cost code field must match the Premier Cost Item ID. During setup, your team will review the imported activities and confirm the IDs are correctly aligned. You can update display names in Miter to match your field team’s terminology, but the underlying cost code field must remain matched to the Premier Cost Item ID to preserve the mapping. Your Miter implementation team will guide you through this process as part of onboarding.

GL accounts flow from Premier into Miter via API. You maintain your chart of accounts in Premier, and Miter pulls them in through the API sync. You do not need to manually build a matching chart of accounts inside Miter. This means any updates to your Premier GL structure, such as adding new accounts or changing account numbers, can be re-synced into Miter to keep both systems aligned.

Team member records are connected between Miter and Premier through a manual primary key sync. To link a team member, the Miter Team Member ID must be matched to the corresponding Employee ID in Premier. Once the IDs match, timesheet and payroll data flowing between Miter and Premier will be correctly attributed to the right employee in each system. There is no automated CSV export for employee records. During Miter onboarding, your implementation team will walk through the ID-matching process and confirm the setup is complete before go-live.

Yes. Because GL accounts sync from Premier into Miter via API, Miter pulls whatever account structure exists in Premier, including custom charts of accounts. You are not limited to a standard account format. As long as your Premier account setup is complete and active, Miter will import the accounts and make them available for use in payroll and timesheet coding. If you make changes to your Premier GL structure after the initial sync, you can re-trigger the sync to update Miter with the latest account list.