> ## Documentation Index
> Fetch the complete documentation index at: https://docs.denari.com/llms.txt
> Use this file to discover all available pages before exploring further.

# That looks wrong

> Most surprises in Flows have a specific reason. Here are the common ones.

## Setup and projects

<AccordionGroup>
  <Accordion title="No projects were made for this engagement.">
    The engagement may still be a draft: an admin needs to click **Activate**.
    If it's active, the service's creation trigger may not have come yet. Admins
    can click **Generate projects** to make anything due now. See
    [Projects](/flows/projects#how-projects-get-made).
  </Accordion>

  <Accordion title="I added a service but only one project showed up.">
    Projects are made on the service's own schedule, a few periods ahead at
    most. More appear as their trigger dates arrive. If the service uses
    **Prior period completion**, only the first project is made today; switch it
    to another trigger.
  </Accordion>

  <Accordion title="I don't see next year's projects.">
    Flows only looks a little way ahead. Future projects appear as their time
    comes.
  </Accordion>

  <Accordion title="The project has a due date I never set.">
    Due dates come from the service's rule, counted from the period (for
    example, *25 days after the period ends*, or *April 15*). See [Service
    templates](/flows/service-templates#what-a-template-holds).
  </Accordion>

  <Accordion title="I changed a template and nothing changed on my clients.">
    Templates only change what future engagements start with. To change one
    client's tasks, edit the tasks on that client's service. See
    [Engagements](/flows/engagements#change-an-engagement-later).
  </Accordion>

  <Accordion title="I can't remove a service.">
    It already made projects. Set **End service on** instead. No new projects
    are made after that date, and existing work is kept.
  </Accordion>

  <Accordion title="I can't archive an engagement.">
    It already made projects. Use **Deactivate** instead.
  </Accordion>
</AccordionGroup>

## Tasks

<AccordionGroup>
  <Accordion title="This task won't let me start it.">
    It's blocked. Either the work before it isn't done yet, or it's on hold.
    Open it to see which. See [Task rules](/flows/task-rules#task-statuses).
  </Accordion>

  <Accordion title="This task has no owner.">
    It's in **Available work**, waiting to be claimed. Either its Assign to
    setting is **Unassigned**, it's **Same as group** and no group above it has
    an owner, or the seat it goes to (such as Tax Manager) is empty for that
    entity. Fill the seat on the client page, or claim or assign the task.
    See [Task rules](/flows/task-rules#how-tasks-get-their-owners).
  </Accordion>

  <Accordion title="The task went to the wrong manager.">
    *Manager* means the entity's manager for that service's category. A tax task
    goes to the Tax Manager. Check the entity's [relationship
    roles](/flows/clients-and-entities#relationship-roles-who-plays-which-part).
  </Accordion>

  <Accordion title="I can't mark this task done.">
    It's time-tracked and has no time logged. Log time first. Or it's blocked.
  </Accordion>

  <Accordion title="The hold came off by itself.">
    Someone logged time to the task. Logging time means work is happening, so
    the hold comes off.
  </Accordion>

  <Accordion title="A task I finished shows &#x22;untracked&#x22;.">
    It's time-tracked and was marked done with no time, or its only time entry
    was deleted.
  </Accordion>

  <Accordion title="I extended the due date but some tasks didn't move.">
    Only tasks that aren't done move. Tasks with chained due dates work out
    their own dates from the task before them. See
    [Projects](/flows/projects#change-a-projects-due-date).
  </Accordion>
</AccordionGroup>

## Time

<AccordionGroup>
  <Accordion title="My hours changed when I saved.">
    Your firm rounds time to a set step, such as 6 minutes. See
    [Time](/flows/time#rounding).
  </Accordion>

  <Accordion title="I can't pick the task I want in a time entry.">
    Only tasks for the same entity that are ready to work on (not done, not
    blocked) can be picked, and all the tasks on one entry must be in the same
    project.
  </Accordion>
</AccordionGroup>

## Billing

<AccordionGroup>
  <Accordion title="Why is all this work on one invoice?">
    One billing group, one billing period, one invoice, with a section for each
    engagement. For separate invoices, split the entities into separate [billing
    groups](/flows/billing-groups).
  </Accordion>

  <Accordion title="Why is this work not on the invoice?">
    Open the invoice's **Billing review** tab. The reason will be there:
    **Covered by plan**, **Budget exhausted**, **Held**, or **Below threshold**.
    Or the work was dated after the cutoff and will be on the next bill. See
    [Drafts & review](/flows/drafts-and-review#the-billing-review-tab).
  </Accordion>

  <Accordion title="A September project showed up on an October bill.">
    The bill for September cut off before the end of the month (for example, on
    the 27th), so late-September work rode the next bill. It's still September
    work. See [The two clocks](/flows/billing#the-two-clocks).
  </Accordion>

  <Accordion title="A date looks one day off.">
    Billing dates, and dates Flows fills in for you such as an invoice date or a
    payment's **Received on**, follow your firm's day, in its time zone. Due
    labels in My Work and the day your time goes on follow your own computer. If
    you work in another time zone, the two can be a day apart late in the
    evening. Your firm's time zone shows on **Billing groups**, under
    **Scheduled billing runs**.
  </Accordion>

  <Accordion title="Flows won't let me start a payment plan last month.">
    A schedule starts this month or later. Each invoice only takes the charges
    due in its own month, so a charge dated in a month that's already over would
    never be billed. See [The billing
    step](/flows/engagements#bill-on-a-schedule-instead).
  </Accordion>

  <Accordion title="My quarterly invoice has three bookkeeping lines.">
    That's right. Each month is its own project, and the quarterly invoice
    gathers all three.
  </Accordion>

  <Accordion title="I changed a price but an existing project didn't change.">
    A project is priced as of the first day of its period. A change only reaches
    periods that start on or after its effective date. See
    [Pricing](/flows/pricing#change-a-price).
  </Accordion>

  <Accordion title="The billing run stopped and says &#x22;Halted&#x22;.">
    Two exclusive arrangements claim the same work. Flows won't guess. Fix the
    scope on one of them and refresh the draft.
  </Accordion>

  <Accordion title="Can I refresh a draft more than once?">
    Yes, as many times as you want while the period is open. It updates the same
    draft.
  </Accordion>

  <Accordion title="I need to fix an invoice I already issued.">
    Void it if no money has been applied. Otherwise, issue a [credit
    note](/flows/credit-notes).
  </Accordion>

  <Accordion title="Why is WIP negative?">
    You've billed ahead of the work. That's normal with fixed fees, retainers,
    and pre-bills. See [WIP & budgets](/flows/wip-and-budgets).
  </Accordion>

  <Accordion title="The invoice says paid but the money isn't in the bank.">
    Card and bank payments show success before the money settles. Settling can
    take a few days.
  </Accordion>

  <Accordion title="An invoice went from paid back to partially paid.">
    A payment was reversed: a refund, a returned bank payment, or a disputed
    card charge. The payment history shows it.
  </Accordion>

  <Accordion title="The client overpaid.">
    Nothing to fix. The extra becomes account credit and is applied to their
    next invoice.
  </Accordion>

  <Accordion title="The draft wasn't sent to the client.">
    Drafts are never sent. An invoice is only emailed after it's issued, on the
    **Send on** date if one was set. See [Issuing &
    sending](/flows/issuing-and-sending).
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.