Fiscal year dates

I would like to associate fiscal year dates with customer records.  So for example, customer A may have a fiscal year that goes from July 1 to June 30. 

Does anyone know if there an easy way to do this so that when you're running reports/charts, you can query on data and organize it by fiscal year.?





I'm not totally clear on your structure, but it sounds like you have a Customer table and then you have other tables with records that are associated with a specific Customer. Typically you would organize reports by your fiscal year, but it sounds like you want to organize reports based on the Customer's FY. So, here is a suggestion:
(1) Create multi-choice fields in your Customer table for "FY Start Month" and "FY Start Day" (you can create them as numeric fields and then change them to multi-choice to ensure valid data).
(2) Create numeric lookups of those fields using the same names in whatever tables you will want to calculate the FY based on a date entered and compared to that Customer's FY.
(3) For each Date field that you will want to group by FY in reports, create a matching FY field. For example, if each Customer had many Projects and you had a Project Start Date, you could create a formula-text field for Project FY Start. The formula to get a result of "FY2010" would be something like:
var number projyr=Year([Project Start Date]);
"FY" &
If([Project Start Date] >=Date($projyr, [FY Start Month], [FY Start Day]),
Sum($projyr, 1), $projyr)
If you are not going to require the Customer to have a Start Month and Start Day, you could enhance the formula to assume Jan 1 for any Customers that don't have a month entered, and could assume the 1st of the month if they only have a month and not a day.
Hope that helps,


Was this answer helpful? Yes No
keirab , QuickBase Solution Provide
QuickBase Solution Provider
5 additional answers

No answers have been posted

More Actions

People come to QuickBase Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

  1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
  2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
  3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
  4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
  5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.

Select a file to attach:

Do you still have a question?

Ask your question to the community. Most questions get a response in about a day.

Post your question to the community