Documentation / Answers / Workday journal pull
Workday journal pull
Last reviewed Nov 19, 2026.
Short answer. Workday pulls a locked month from Meridian and posts it with Submit Accounting Journal. Create a GL export key on Meridian Settings, then an inbound EIB whose REST URL ends in /v1/meridian/gl-export/workday/next. User Id is the key's public id. Password is the secret, shown once. Run Validate Only on a sandbox tenant, then schedule the EIB monthly after the Meridian close. A failed run is read under the integration event, Document Retrieval, then Errors.
Meridian does not store a Workday user name, password, certificate, or token. Workday stores the Meridian key. You need an organization admin in Meridian and someone who can create an inbound EIB in Workday. Lock the month on Chargeback, and make the Workday export checklist green, before the first run.
1. Create the key
- Sign in to Meridian.
- Open Settings.
- Open the Workday card.
- Type a name, such as Workday, and choose Create.
- Copy the public id. That value is the EIB User Id.
- Copy the secret. That value is the EIB Password.
The secret is shown once. If you leave the page without copying it, revoke that key and create another. The card keeps the public id, the last used time, and each pull and refusal.
2. Create the inbound EIB
In Workday, choose Create EIB, then Inbound. Use these settings. Leave Data Format as it is. It is display-only and already shows REST URL.
| Setting | Value |
|---|---|
| Get Data | REST URL |
| REST Endpoint | https://api.onaro.io/v1/meridian/gl-export/workday/next |
| User Id | the key's public id |
| Password | the secret |
| Data Format | Leave it. Display-only, shows REST URL. |
| Transform | Template Model, Submit Accounting Journal |
| Deliver | Workday Web Service Operation, Submit Accounting Journal (Web Service) |
Do not put the key in the URL. A test before this is on production uses https://api-staging.onaro.io/v1/meridian/gl-export/workday/next with the same user id and password.
next sends the earliest locked month this key has not already received, once that month is ready. A later month waits until the earlier one has been sent. For one named month, replace next with periods/2026-11. That address can return a month this key already received. latest always returns the newest locked month, including one already sent.
3. Run Validate Only
Launch the integration and run Validate Only on a sandbox tenant first. A locked ready month that this key has not received loads one record and zero failed. The Workday card in Meridian shows that pull.
4. Schedule it monthly
Open Launch / Schedule Integration. Set the run frequency to monthly. Schedule it a few days after the usual Meridian close, so the month is locked before the run.
A run before the next month is locked does not post the same journal again. Workday marks that run Failed (Critical). The error under Document Retrieval is “Nothing new to send.” That status is expected and harmless.
5. Read a failed run
The line at the top of a failed run is generic: “A processing fault occurred.” Open the integration event, then Document Retrieval, then Errors. That block shows the HTTP status and the response body. The Meridian sentence is at the start of the body. The fix for each sentence is on GL export troubleshooting.
6. Revoke or rotate the key
On Settings → Workday, choose Revoke on the key. The next run then gets “The Meridian key was refused.” Create a new key, copy the new public id and the new secret, and replace the User Id and Password on the EIB. Leave the old key revoked.
A new key has not received a month. Each run sends the earliest locked ready month that key has not received. A month already posted in Workday fails at Data Load with “The Accounting Journal is posted or canceled or is an intercompany or reversal journal and cannot be submitted.” That month is already in Workday. No action is needed. The following run moves to the next month.