Close Help Center

How to Register an Income

Update the ProcessFlex knowledge base article about income registration, including a complete explanation of the recurrence functionality, using icons (emojis) to improve readability and scannability.

---

🎯 Objective

Create a clear, well-structured, and user-friendly article, maintaining consistency with the ProcessFlex Help Center standards.

---

🧱 Required Article Structure

The article must include the following sections:

📥 Title

How to register an income in ProcessFlex

📍 Step-by-step

  • Navigation: Finance > Statement
  • "Income" button
  • Modal opening

📝 Required Fields

List and explain:

  • Amount 💰
  • Date 📅
  • Bank Account 🏦
  • Chart of Accounts 📊
  • Cost Center 🧩
  • Payment Method 💳

---

🔁 Recurring Income

Clearly explain:

  • What recurring income is 🔄
  • When to use it 📌
  • That the system automatically generates future entries ⚙️

---

⚙️ Recurrence Fields (mandatory details)

Explain all fields displayed when recurrence is enabled:

  • Recurrence 🔁

Frequency of repetition (monthly, weekly, yearly, etc.)

  • Start date 📅

Base date for generating future entries

  • End date(optional)

Defines until when the recurrence will be valid

  • Incidence type 🧠

Defines the recurrence logic

(e.g., day of the month, day of the week)

  • Incidence day 📌

Defines the specific day of generation

(e.g., day 3, Monday)

  • System automatic message 💡

Explain that the system displays a summary of the rule

(e.g., “It will be created every month on day 3”)

---

🔎 Additional Fields (optional)

List with icons:

  • Source Process (purchase, sale, quotation, or any process linked to the income) 🔗
  • Description 📝
  • Currency 💱
  • Tag 🏷️
  • Payee: A profile registered in the system linked to the payment, such as a customer 👤

---

💰 How records are generated

Explain:

  • Income → value inflow ➕💰
  • Expense → value outflow ➖💰
  • Recurrence → automatic generation of future entries 🔄

---

✍️ Writing Guidelines

  • Use simple, direct, and user-oriented language
  • Avoid unnecessary technical terms
  • Use emojis consistently (but not excessively)
  • Maintain clarity and visual organization
  • Content must be ready for publication (no internal explanations)

---

✅ Expected Outcome

A complete Markdown article, well formatted, using icons, ready for publication in the ProcessFlex Help Center.