DAV Integration
Connect awork with Die Agenturverwaltung (DAV) to sync projects, tasks, time entries, and absences between systems while keeping commercial data separate in DAV
This article explains how to set up the DAV integration, which data is synchronized between the systems, and what you can do if projects or time entries aren't transferred as expected.
Benefits and typical use cases
The DAV integration connects awork with Die Agenturverwaltung (DAV). Each system keeps its own responsibilities: DAV manages commercial data, while awork manages day-to-day work. This lets projects, tasks, and time tracking work together without transferring prices, euro budgets, or invoices to awork.
| Data | Direction | What happens |
|---|---|---|
| Estimates (KVs) and items | DAV → awork | KVs become task lists, and items become tasks with the corresponding planned effort |
| Clients | DAV → awork | The client associated with the DAV budget is assigned to the awork Projekt |
| Time entries | awork → DAV | Time entries recorded in awork are created, updated, or deleted in DAV unless a protection rule applies |
| Project links | awork → DAV | awork writes project links to the Awork Link job field |
| Approved absences (optional) | DAV → awork | Absences that reduce capacity in DAV are transferred to awork |
Important: Prices, budgets in euros, invoices, and retainer objects stay in DAV. awork imports the planned effort for items; the awork Projekt budget is the sum of these planned efforts.
Key terms
| Term | Meaning |
|---|---|
| Job | A client order with its own project number. DAV calls jobs "Projekte" in its interface. Time entries are recorded against the job or one of its KV items. |
| Budget | A client budget with its own price list, for example, for a brand. The budget can determine which project template awork uses. |
| KV (estimate) | A quote for a job with items and a status. When transferred, a KV becomes a task list in awork. |
| internal hour services | An item delivered by the agency itself. It becomes a task in awork with planned effort, provided DAV supplies the corresponding hours. |
| External service | A purchased item. It becomes a task in awork with the "Fremdleistung" tag and no planned effort. |
| Function | An activity with an hourly rate in DAV, for example, "Design." Each DAV user has one or more functions, including a default function. Functions are mapped to awork activities by name. |
| Reference number | A value in a KV field, often "Kundenreferenz," such as an item number. When grouping by "Job und Kennziffer," KVs with the same reference number within the same job share an awork Projekt. |
| Budget mode | A DAV job with planned hours for each function, even if it has no KV. In awork, this creates tasks in the "Geplante Budgets" list. |
| Retainer KV | A KV with recurring invoices, for example, monthly invoices. Retainer KVs aren't transferred to awork by default, but you can enable their transfer. |
| KV status | The processing status of a KV. It helps determine whether the KV is transferred and whether new time entries can be booked against its items. |
| "Sync zu awork" | A checkbox on KVs and jobs in DAV. A KV is marked for transfer if the checkbox is selected on the KV or its job. |
| Awork Link / Awork-Link | DAV fields used to link to awork Projekt: "Awork Link" on a job and "Awork-Link" on a KV. |
Requirements for setup
Make sure the following requirements are met before setting up the integration:
-
One DAV tenant per awork workspace
-
An API key from a DAV admin with permission to read jobs, KVs, users, and absences, and to book time for other users
-
Matching user email addresses: The work email address in awork must match the DAV user's email address
-
At least one function for each DAV user who needs to book time in DAV
-
DAV fields for synchronization: The Sync zu awork field must be available on KVs and jobs
-
DAV fields for project links: Awork Link on jobs and Awork-Link on KVs must be available
DAV must create the custom fields. The DAV API can't create these fields itself. awork identifies the project link fields by their technical name, awork_link, not by their displayed label. By default, the synchronization field uses the technical name sync_to_awork.
If you want to group projects by reference number, you'll also need a KV field containing the reference number.
How to set up the DAV integration
1. Prepare DAV
-
Sign in to DAV as an admin and go to Einstellungen → Integrationen → API-Schlüssel → Persönliche Zugriffstoken → Neues Token erstellen. The API key inherits the permissions of the user who creates it. This user must be allowed to read all jobs, KVs, users, and absences, and to book time for other users.
-
Assign each DAV user the functions they should be able to book time against: Einstellungen → Benutzerverwaltung → Benutzerliste → User → Reiter Zeiterfassung. Every DAV user who needs to receive time entries must have at least one function. DAV rejects time entries if no function is assigned.
-
Make sure the user email addresses match in DAV and awork. You can find the DAV email address under Einstellungen → Benutzerverwaltung → Benutzerliste → User → Reiter Stammdaten. awork uses the user's work email address for matching. If no work email address is set, awork uses the login email address. You can't match users manually.
-
Ask DAV to create the required custom fields:
- Sync zu awork on KVs and jobs
- Awork-Link on KVs and Awork Link on jobs
-
If needed, enter the reference number in the desired KV field on the Kostenvoranschlag tab. The "Kundenreferenz" field is often used for this.
-
In DAV, mark the KVs or jobs you want to transfer to awork.
Important: DAV must create the custom fields. If the synchronization field is missing, you won't be able to save the integration.
The project link fields aren't checked when you save. awork doesn't identify them by their displayed labels. If the project link fields are missing, awork won't write any project links to DAV and won't show an error. You also won't be able to link projects manually using these fields.
2. Contact support
- In awork, open Einstellungen (the gear icon in the bottom-left corner of the main menu) > Integrationen. Click the Integrations-Bibliothek öffnen button and select Die Agenturverwaltung in the Agentursoftware section.
Click Support kontaktieren to open the chat window and contact awork Support. Alternatively, email support@awork.com.
You can't activate the integration yourself. awork Support will set it up for you.
3. Agree on the settings with awork Support
Before setup, discuss the following points:
-
Grouping: Should there be one Projekt per job, per job and reference number, or per KV?
-
KV status: Which status should KVs have before they're transferred?
-
Activities for new tasks: Should awork use only existing activities for new DAV tasks, automatically create any missing activities, or leave the activity unset? Activities are mapped using the name of the function on the DAV item. By default, awork creates any missing activities.
-
Projekt duration: Should the start and end dates come from the job, from the KV service periods, or not from DAV?
-
Retainers: Should retainer KVs with recurring invoices be included?
-
Projekt fields: Should "DAV Kennziffer" and "DAV Etat" be created and populated?
-
Projekt templates: Which template should be used for a budget or client, and which template should be the default?
-
Absences: Should approved absences from DAV be transferred to awork?
-
Booking text: Should the task name be added before the booking text?
-
Users without a DAV match: Should a shared user receive their time entries?
-
Time entries: From what date should time entries be transferred? By default, transfer starts on the setup date; earlier time entries are never sent.
-
Existing Projekt: Should existing awork Projekt be linked to KVs or jobs?
4. Test the transfer
-
In DAV, select a quote with at least one external service and set it to a transferred status, such as Freigabe
-
Ask Support to start the sync, or wait for the next sync
-
In awork, check that the project, task list, task with planned effort, and expected project fields are present
-
Log a test time entry on the task and check in DAV that the job, position, and function are correct
How synchronization works
Each transferred quote becomes a task list in an awork Projekt, and each position becomes a task. The grouping determines which quotes share a project.
Which quotes are transferred
A quote is transferred only if all the following conditions are met:
-
The quote or its job is marked Mit awork synchronisieren. A marked job also includes any quotes created later
-
The quote has a status selected for transfer in the integration
-
The job has the status aktiv or abzurechnen in DAV
-
The quote is not a retainer quote, or the transfer of retainer quotes is enabled
You can select these eight statuses for transfer: In Bearbeitung, wartet auf interne Freigabe, wartet auf Versand, wartet auf Freigabe, Freigabe, Auftragsbestätigung, wartet auf Abrechnung, and wartet auf Verrechnung. The statuses „abgerechnet", „gegen Guthaben verrechnet" and „nicht realisiert" cannot be selected.
By default, the statuses Freigabe, Auftragsbestätigung, wartet auf Abrechnung, and wartet auf Verrechnung are enabled.
Note: Retainer quotes are not transferred by default. If you enable them, awork uses the hours provided by DAV and does not automatically divide them by the number of billing periods.
How quotes are assigned to projects
The grouping determines which quotes are added to the same awork Projekt.
| Grouping | One project per | Project name | Project key |
|---|---|---|---|
| Job | Job | Job name | Project number |
| Job und Kennziffer | Job and reference number. Quotes without a reference number share the job project with the planned budgets | Name of the first quote in the group; if there is no reference number, the job name | Project number and reference number; if there is no reference number, only the project number |
| KV | Quote | Quote name | Quote number |
Project key: For automatically created projects, awork builds the key from the project number, the project number and reference number, or the quote number, depending on the grouping. The key can be up to 32 characters long. If it is already in use or is too long, awork builds it from the project name instead. The project key is set only when the project is created.
With the Job und Kennziffer grouping, quotes with the same reference number in the same job belong to the same project.
After a quote is first transferred, it stays in that project. Changing the grouping, reference number, or status later, or moving the quote to another DAV job, does not automatically move it to a different project.
Manually linking existing awork projects
You can link a quote or job to an existing awork Projekt. To do this, enter the project link or project key in the corresponding DAV field: Awork-Link on the quote or Awork Link on the job.
Linking a project through a DAV link field is not the same as entering a DAV job number in the awork Projekt field DAV Projektnummer. The differences for time entries are described in Which job or position time is booked to.
For a link on a quote:
- The link is only used while the quote has not yet been assigned to an awork Projekt.
- awork ignores any later changes to the link.
For a link on a job:
- The link is only used while the job does not yet have an awork Projekt.
- It applies to the job's planned budgets.
- With the Job grouping, it also applies to all quotes in the job.
- With the Job und Kennziffer grouping, it applies only to quotes without a reference number.
- As soon as the job has awork projects, awork writes their links to the job field as a comma-separated list. awork does not populate the quote field Awork-Link.
- awork updates the job field only when the list of associated awork projects changes. If you edit the field manually in DAV, your change remains until then.
For a quote with a link, awork uses the first matching rule:
- If the linked project already belongs to a DAV group, the quote is added to that project.
- If the quote's group does not yet have a project, the linked project is assigned to the group. Any quotes from that group transferred later are also created there.
- Otherwise, only that quote is assigned to the linked project.
The manually linked project keeps its name, project key, customer, and template. The start date, end date, and project budget come from DAV. awork adds the task lists, tasks, and DAV project fields.
Time logged on tasks that are not linked to a DAV position is booked to the DAV job.
Important: If the link does not point to a usable project, the transfer of the quote or job group is paused. awork will not create a new project as a fallback. Correct the link in DAV and ask awork Support to run the sync again.
What a quote becomes in awork
awork uses the customer from the DAV budget. The DAV ID ensures that the same awork customer remains linked even after a name change. If no match is found, awork looks for a customer with the same name or creates one. The DAV customer number appears on the awork customer as the contact info „DAV-Kundennummer".
-
Quote: Becomes the task list „KV-Nummer - KV-Name"
-
Position: Becomes a task. If there is a position group, the name is usually „Position group - position". If the group name is missing or is the same as the position name, awork uses only the position name
-
Description: The position text from DAV becomes the task description
-
Project description: For an automatically created job project, awork imports the DAV job description only when creating the project. The project description remains blank for other automatically created projects.
-
External service: The task gets the tag „Fremdleistung" and no planned effort
-
Project budget: Equals the total planned effort of the DAV tasks
-
Project owner: When the project is created, awork assigns the responsible user from the DAV job, if there is a matching awork user
DAV generally calculates a position's labor-time budget from the net amount and the hourly rate for the function in the budget's price list. For positions without a function, DAV uses the average rate in the price list or, after the first time entries, the average of the time logged. If the price list has no hourly rates, the labor-time budget calculated by DAV is 0. In that case, awork can use the position quantity as planned effort if the unit is „Std.", „Stunden" or „h". External services do not receive planned effort.
For approved quotes, DAV calculates planned effort from the monetary amount. For quotes that have not yet been approved, awork uses the position quantity as planned effort only if the unit is hours. Fixed-price positions have no planned effort before approval. The values may change once the quote is approved.
Project templates, durations, and project fields
When creating a new project, awork selects the first matching template in this order:
- An awork Projekt with the same name as the KV template in DAV. DAV only provides the KV template name for KVs created from a template on or after October 26, 2026.
- The template assigned to the budget.
- The template assigned to the budget's customer.
- A template with the same name as the budget.
- The default template.
- No template, if none of the rules apply.
Assignments to budgets and customers remain in place even if they are renamed. If an assigned awork template is no longer available, awork uses the next matching rule.
Each DAV line item is created as a separate task. awork does not automatically link it to a task with the same name in the project template. So use templates for phases and internal hour services, not for copies of KV line items. Otherwise, duplicate tasks may be created. Time logged on tasks from the project template is assigned to the DAV job.
You can move a task created from DAV to another task list in the same awork Projekt. The integration will not move it back to the original KV list. The link to the DAV line item remains in place, and time logged on the task continues to be assigned according to the rules for that line item.
You can choose whether to import start and end dates from the KV service periods, from the job's start and end dates, or not at all. With the automatic option, a job project uses the job's start and end dates. For other projects, awork uses the earliest start date and latest end date of the KV service periods.
If the integration should not import durations from DAV, the project manager maintains this information in awork. The integration will not change it.
When needed, awork creates these project fields:
- DAV Projekt: Link to the DAV job.
- DAV Projektnummer: Job number as a text field.
- DAV KV-Nummer: Project KV numbers as a text field, separated by commas.
- DAV Kennziffer: KV codes as a text field, if this option is enabled.
- DAV Etat: Budget name as a dropdown field, if this option is enabled.
The first three fields are always used. Existing values in optional fields remain if the relevant option is later disabled. DAV Etat is a dropdown field, not a tag.
The integration does not set additional project members, task assignees, project status, or project type.
Jobs in budget mode
A job marked as being in budget mode gets a project even if it has no KV. With the "Job" grouping, it uses the project for its KVs. With "Job and code", it uses the project for its KVs without a code. The task list is called Geplante Budgets. A task is created for each budget line, with a name and function where available. The planned effort matches the planned hours for that line.
If the request fails, awork skips the job. Contact awork Support if planned budget lines are missing.
What changes after the first transfer
After the first transfer, awork updates the data imported from DAV according to the following rules. Projects, tasks, and time already recorded are not simply deleted when data changes or is removed in DAV.
-
New KVs and line items: New KVs are added as task lists, and new line items as tasks, to the appropriate awork Projekt.
-
Changed line items: If the name, line item text, or hours change in DAV, awork updates the task name, description, and planned effort. If no line item text is available in DAV, the awork description remains unchanged. If no hours value is available, the existing planned effort is kept. Assignees, dates, and task status are not changed.
-
Changed KV name or KV number: awork renames the corresponding task list.
-
Project data changed in DAV: The project name and project budget are updated with the values from DAV. Start and end dates are imported according to the selected duration setting. If durations are not imported from DAV, the dates maintained in awork remain unchanged.
-
Removed line items or deleted KVs: The corresponding tasks remain in awork and get the tag "in DAV entfernt". New time logged on these tasks is assigned to the DAV job. Time entries that have already been transferred are reassigned to the job the next time they are changed. If a line item is restored, awork removes the tag. A deleted KV no longer counts toward the project name, project budget, or DAV project fields.
-
Switching between agency services and external services: The task and any time already recorded remain in place. If a line item becomes an external service, the task gets the tag "Fremdleistung" and loses its planned effort. If it becomes an agency service again, awork removes the tag and imports the planned effort according to the rules for agency services.
-
A KV leaves the statuses selected for transfer: The project and tasks remain in place, but are no longer updated for this KV. The KV continues to count, using the values from its last sync, toward the project name, duration, budget, and the "DAV KV-Nummer" and "DAV Kennziffer" fields. New time is assigned to the job as long as the KV or its job is still marked Sync zu awork. If neither is marked, no time is sent to DAV. Existing time entries remain assigned to their line items and can still be updated as long as the KV is not "abgerechnet" or "gegen Guthaben verrechnet". For these two statuses, awork does not send changes or deletions for time entries on KV line items.
-
The sync marker is removed from the KV and job: The project and tasks remain with the last synced KV data, but are no longer updated. In addition, no time entries, changes, or deletions are sent to DAV for the KV or job that is no longer marked. If no KV or job in the project is marked for sync, this applies to all time entries for the project. If the marker is added again, syncing continues in the same awork Projekt. The overnight sync then sends changes to time entries from the last 14 days and processes any pending deletions. The safeguards for billed KVs and entries changed or deleted directly in DAV still apply.
-
The code of a KV that has already been transferred is changed: The KV stays in its existing awork Projekt. The "DAV Kennziffer" project field is updated if populating this field is enabled. Changing the code does not automatically move the KV to another project.
-
A KV is reassigned to another job in DAV: The KV stays in the awork Projekt it was first assigned to. Its tasks get the tag "in DAV umgebucht" and can be moved manually if needed. Time logged on these tasks is assigned to the new DAV job and its line items. If the KV is reassigned to its original job, awork removes the tag. Exception: With the KV grouping and with a manually linked project, the awork Projekt follows the new DAV job. In these cases, the "in DAV umgebucht" tag is not applied.
-
A task or project is edited in awork: Changes made in awork remain until the corresponding data changes in DAV. If the line item changes in DAV, or the project name, duration, or budget changes, awork imports the relevant values from DAV again. Start and end dates are only imported if the duration setting allows it.
-
A DAV task is deleted in awork: awork recreates the task as soon as the corresponding line item changes in DAV. So deleting a task in awork does not permanently prevent the line item from appearing again as a task.
-
A linked project is deleted in awork: The corresponding DAV group is no longer transferred. If you restore the project from the trash, the overnight sync links it with DAV again.
-
A task is created manually in awork: The task remains in place and is not removed by the integration. Time logged on this task is assigned to the DAV job, not to a KV line item.
-
The awork link of a KV that has already been assigned is changed: awork ignores the change. A link on a KV is only taken into account while the KV has not yet been assigned to an awork Projekt.
-
The customer number is changed in DAV: The "DAV-Kundennummer" contact info on the awork customer is updated the next time data is retrieved. If there is no longer a customer number in DAV, awork removes the contact info. If you change the contact info directly in awork, that change remains until the customer number changes in DAV again.
Note: Changes to the grouping and to the setting for transferring retainer KVs only apply to KVs that have not yet been assigned to an awork Projekt. They do not automatically move or remove KVs that are already assigned.
How time tracking works with DAV
awork is the source of truth for time tracking. A time entry on a DAV project is created, changed, or deleted in DAV as soon as you save it in awork. Changes made directly in DAV are not synced back to awork.
Who receives the time in DAV
awork first matches the time entry to the DAV user with the same work email address. If there's no matching user, a catch-all user configured during setup can receive the time. If there's no match and no catch-all user, the time won't be transferred.
A DAV user needs at least one function. awork selects the function for a booking in this order:
-
The user's function whose name matches the time entry's activity
-
The function of the position or budget line, if the user has that function
-
The user's default function
If awork can't find a matching function based on the activity or position, it uses the DAV user's default function. If the DAV user has no function at all, the booking fails.
awork matches a time entry's activity to a DAV function by name. Renaming a function can break this name-based match. If that happens, awork uses the function of the position or budget line, if the DAV user has it. Otherwise, it uses the user's default function.
When a catch-all user is used, the booking text also starts with the name of the awork user whose time is being transferred.
Important: A time entry that has already been booked to your own DAV user won't be reassigned to the catch-all user. If the match to your own DAV user is lost, the next change to that entry will fail. In this case, correct the email mapping. Support must then first run a KV reconciliation and resend the affected time entries afterward.
Which job or position the time is booked to
-
Task on a KV position: For a project created by the integration or manually linked through a DAV link field, the KV or its job must still be marked Sync zu awork. If so, new time is booked to the position if it still exists, allows time tracking, and its KV has a status selected for transfer. Otherwise, new time is booked to the job. If neither the KV nor its job has this setting, the time won't be transferred.
-
Other project tasks: Time on template tasks, custom tasks, and budget lines is booked to the job.
-
Project with a DAV project number: Time can be booked to the job with this number, even if the awork Projekt didn't originally come from DAV.
-
Project with no DAV connection: Time won't be transferred to DAV.
awork uses the task and project to determine where to book time. Tags such as "Fremdleistung" don't redirect time. Time on subtasks is treated the same way as time on the main task. If DAV doesn't recognize a number entered in the DAV Projektnummer project field, awork skips the time without showing an error.
Two different types of connection:
-
Projects created by the integration or manually linked through a DAV link field: Failed time bookings from the last 14 days are retried during the nightly reconciliation.
-
Projects connected only through "DAV Projektnummer": awork books the time to the DAV job with that number. awork doesn't check whether Sync zu awork is enabled. Failed time bookings aren't automatically retried during the nightly reconciliation. Contact Support to request a manual resend if needed. If DAV doesn't recognize the job number you entered, awork skips the time without showing an error.
Which time data is transferred
- Date: The calendar day of the time entry in its time zone.
- Duration: Exact to the second, with no rounding.
- Text: The time entry's note. If there's no note, awork uses the task name. If the option to prepend the task name is enabled, the text is "Task, note" when a note is available.
- External ID: The ID of the awork time entry. It links the entry in awork to the booking in DAV.
This link prevents duplicate time entries in DAV when entries are resent. The nightly reconciliation resends changed entries as a precaution.
For bookings made to a catch-all user, the name of the awork user whose time is being transferred is also added at the start of the text.
Start and end times, and whether an entry is billable, aren't transferred. Running timers are sent only after you stop them. Time entries dated before the configured cutoff date are never transferred.
Changes, deletions, and protected time bookings
If a KV in DAV has been invoiced or offset against a credit balance, time bookings on its positions are locked. awork won't send changes or deletions for these entries to DAV.
This also applies if you move such a time entry to another task. awork enforces this restriction; DAV itself doesn't lock these entries.
If an entry has been changed or deleted in DAV, awork also protects the version in DAV. Before making a change or deletion, awork checks the entry in DAV. If the job, position, function, user, date, or duration differs from the last version awork sent, or if the entry has been deleted in DAV, awork won't send an update, deletion, or new entry. The text isn't checked in this comparison.
If you move a time entry that's already been transferred to an awork Projekt with no DAV connection, awork deletes the corresponding booking in DAV. This doesn't apply if a protection rule is triggered, for example because the KV has already been invoiced or the entry was changed directly in DAV.
If a KV simply no longer has a status selected for transfer, existing time entries remain on their positions. Changes to them will still be sent to DAV, provided the KV or its job is still marked for sync and no protection rule applies. Under the same conditions, new time is booked to the job. If neither the KV nor its job is marked for sync, awork won't send time bookings, changes, or deletions for that KV.
The nightly reconciliation retries failed time bookings from the last 14 days only for projects created by the integration or manually linked through a DAV link field. Projects connected only through DAV Projektnummer aren't retried automatically. Support can manually resend these bookings, as well as older failed entries.
Importing absences from DAV
The transfer of approved absences can be disabled during setup. It's enabled by default. It runs only from DAV to awork and includes only absence types that reduce capacity in DAV, such as vacation. Working from home isn't imported.
-
Only users with a matched DAV user receive synced absences.
-
A DAV request is imported as an awork absence, even if DAV stores it as individual days.
-
Changes to the dates in DAV update the awork absence.
-
Canceled, rejected, or deleted absences are removed from awork.
-
A single half day remains a half day. Half days within multi-day requests are converted to full days.
-
Each sync retrieves absences from the previous 60 days and up to 400 days into the future.
Important: If you already sync absences from another system, such as Personio, leave this option turned off. Otherwise, duplicate absences may be created.
When synchronization runs
-
Regular polling: Every five minutes by default. You can set the interval to anywhere from 1 to 1,440 minutes.
-
Webhook from DAV: Changes to estimates, jobs, budgets, or customers can trigger an immediate poll.
-
Nightly reconciliation: Every day between 2 and 5 a.m. UTC, awork rereads estimates, checks linked projects, resends changed time entries, and attempts to catch up on failed time entries from the last 14 days and deletions from the last 48 hours.
If no webhook is registered, regular polling continues. Changes in DAV are then detected during the next poll. Absences are not reconciled during the nightly run. If two awork workspaces use the same DAV tenant, only one receives webhooks. The other uses regular polling.
Note: If DAV recalculates planned effort without the estimate changing, awork can only pick up the new value during the nightly run or after the next change to the estimate.
Integration limitations
-
An estimate stays linked to the awork Projekt it was first assigned to. Changes to the grouping or identifier do not move it automatically. Reassigning it to another DAV job also does not move the estimate to a different awork Projekt. However, with the Estimate grouping and with a project linked manually via the DAV link field, the project assignment follows the new DAV job. For details, see What changes after the initial transfer.
-
Functions and activities are matched by name. If the names do not match, the fallback rules under Who receives the time in DAV apply: the function assigned to the position or budget line, followed by the DAV user's default function.
-
Two awork workspaces with the same DAV tenant: Only one receives webhooks. The other uses regular polling. See the section on timing.
Troubleshooting tips
If you run into a problem, first check the data and settings in DAV. If you need another sync or an integration check, awork Support can help.
Notes:
- After making corrections in DAV: If you changed user email addresses, user functions, or position data such as the time tracking setting or estimate status, Support must first start an estimate sync. This is the only way awork rereads this data. After that, the affected time entries can be sent again.
- If the integration is turned off, manual syncs are not possible. After an interruption of more than 14 days, older failed time entries and changes to older time entries will no longer be caught up automatically. After reactivating the integration, ask Support to manually resend the time entries for the affected period. Safeguards for invoiced estimates and entries changed or deleted directly in DAV still apply.
Tip: Ask the awork Agent (🔐 available starting with the Standard Plan) to analyze any issues and help narrow down their causes. The awork Agent analyzes the available execution logs.
An estimate is missing in awork
Check the following in DAV:
-
Is Mit awork synchronisieren enabled on the estimate or its associated job?
-
Does the estimate have a status that is included for transfer in your integration?
-
Is the associated job set to aktiv or abzurechnen?
-
Is it a retainer estimate? These are not transferred by default.
If you linked an existing awork Projekt using the Awork Link field on the job or Awork-Link field on the estimate, check that a valid project link or project key is entered.
The next sync may not have run yet. If the estimate is still missing, contact awork Support.
Estimates are no longer updating
Check whether the Mit awork synchronisieren field configured for the integration is still present on the estimates in DAV. If the field is missing under its configured technical name or displayed label, for example because it was deleted or renamed, polling stops. Existing projects remain in place, and time entries continue to be transferred to DAV.
Ask your DAV administrator to restore the field, or ask awork Support to adjust the setting for the sync field.
Important: A missing field is not the same as a removed checkmark. If the field is present but neither the estimate nor its job is checked, no time entries, changes, or deletions for that estimate will be sent to DAV.
An estimate appears in the wrong project
When an estimate is first transferred, it is assigned to an awork Projekt. Later changes to the grouping do not move it automatically.
If the estimate was reassigned in DAV, its tasks in awork may have the tag in DAV umgebucht.
You can move the affected tasks manually in awork. Their time entries will remain assigned to the DAV position. However, new positions for the estimate will still be created in the project it was originally assigned to.
Tasks appear more than once
If your project template already contains tasks that are also transferred from DAV as positions, they may appear more than once.
-
Track time on the task transferred from DAV.
-
Before completing or deleting the task from the template, check whether any time has already been tracked on it.
-
Remove the relevant tasks from the project template to avoid duplicates in new projects.
A task has the tag "in DAV entfernt"
This tag means that the associated position or estimate was removed in DAV.
Check whether you still need the task in awork. You can then complete or delete it. Be sure to account for any time already tracked.
A time entry is missing in DAV
First, check the following:
-
Is the timer stopped? Running timers are transferred only after they are stopped.
-
Is the date on or after the configured transfer start date? Time entries dated before then are not transferred.
-
Is the project linked to DAV? Time entries without a project, or on projects that are not linked to DAV, are not transferred.
-
Is "Mit awork synchronisieren" still enabled? For a project created by the integration or linked via a DAV link field, check the setting on the associated estimate or job. For projects linked only via DAV Projektnummer, this setting is not required to transfer time entries.
-
Do the email addresses match? The business email address in awork must match the DAV user's email address.
-
Does the DAV user have at least one function? DAV cannot accept a time entry for a user who has no assigned function.
For a project linked only via DAV Projektnummer, also check that this project field contains the number of an existing DAV job. Failed time entries for these projects are not automatically retried during the nightly reconciliation. Contact Support to have them sent again.
If you corrected an email address or function and the time entry is still missing, contact awork Support. They can check whether it can be sent again.
Time is booked to the job instead of a line item
For tasks from DAV line items, time is booked to the job only if the estimate or its job is still marked Mit awork synchronisieren. If neither is marked, the time won't be transferred.
This may be expected behavior. Time is booked to the job when:
-
it was tracked on a manually created task or a task from the project template,
-
it was tracked on a task from "Geplante Budgets",
-
the DAV line item doesn't allow time tracking,
-
the estimate no longer has a status that allows it to be transferred,
-
the associated line item has been removed from DAV.
When the estimate status changes, time is booked to the job for new time entries. Entries that have already been transferred remain on their line item. Changes will continue to be sent if the synchronization marker is present and no protection rule applies. For entries marked "abgerechnet" or "gegen Guthaben verrechnet", awork won't send changes or deletions.
Check which task the time was tracked on in awork, and whether the associated DAV line item still exists and allows time tracking.
A time entry has the wrong function in DAV
Check whether the activity of the time entry in awork has the same name as the function you want in DAV, and whether that function is assigned to the DAV user.
If there's no matching function, the integration uses the function assigned to the line item or budget line, if the user has it. Otherwise, it uses their default function.
If needed, correct the names or function assignment. To have existing time entries transferred again, contact awork Support.
Changes to or deletions of time entries aren't showing up in DAV
In the following cases, changes made in awork are intentionally no longer transferred:
-
The associated estimate is marked abgerechnet or gegen Guthaben verrechnet.
-
The time entry was deleted in DAV, or its job, line item, function, user, date, or duration has changed since it was last transferred. Changing only the booking text doesn't trigger this protection.
Check the estimate status and the time entry in DAV. You'll need to make any necessary corrections to these protected entries directly in DAV. Changes made in DAV aren't transferred back to awork.
Project links are missing in DAV or a manual link isn't working
Check whether the Awork Link field is present on the job and the Awork-Link field is present on the estimate.
If the fields are missing or the link still doesn't work despite a valid project link, ask DAV to check the fields and their configuration.
A project, task list, or task was unexpectedly created more than once
Check in awork which items are duplicated and whether they already contain tasks or time entries. Contact awork Support before deleting anything that appears to be a duplicate.
If the creation of a project, task list, or task was interrupted, awork may not be able to tell whether the object was created. In this case, the affected DAV group will be skipped during future syncs, without a new error message each time. Support will need to investigate.
Still having trouble?
Send awork Support a link to the affected awork Projekt, the job or estimate number from DAV, and a brief description. If time entries are missing, also include the date and duration of the affected entry, along with screenshots from awork and DAV.
FAQ
Is the integration paid?
No, the DAV Integration is included in your awork plan.
Can I activate the DAV Integration myself?
No. Please contact awork Support. They'll set up the integration for you.
Which data stays in DAV?
Prices, budgets in euros, invoices, and retainer objects stay in DAV. awork imports estimates, line items, and the tasks and planned effort derived from them.
How often is data synced?
By default, the regular sync runs every five minutes. A registered webhook can trigger an immediate sync when an estimate, job, budget, or customer changes. There's also a nightly reconciliation.
Why isn't my time being transferred to DAV?
Check that the timer was stopped, the date is on or after the configured cutoff date, the project is linked to DAV, and your work email address is the same in both systems. Your DAV user also needs at least one function. If needed, a configured shared user can transfer time entries.
Are changes to time entries in DAV transferred to awork?
No. Changes to time entries in DAV aren't transferred back to awork. If the job, line item, function, user, date, or duration has changed since the last transfer, or the entry was deleted in DAV, awork protects that state: it won't send a change or deletion, and it won't create the entry again. The booking text isn't compared during this check.
Are absences synced in both directions?
No. Approved absences that reduce capacity can optionally be transferred from DAV to awork only. If you already use another system for this, disable DAV absence syncing.
What happens if I deactivate the integration?
Syncing will stop and the webhook in DAV will be disabled. Projects, tasks, and time entries in awork and DAV will remain in place and won't be deleted.
